MailerCheck
for LuumenAI
Check verification lists, results, and credits, then submit new lists for review
Connect MailerCheck and Luumen can read your verification history without leaving the terminal: which lists ran, how many addresses each held, how results broke down by classification, and how many credits remain. When a new list needs to go in, Luumen drafts it from the addresses you give it and shows you the name and count before anything is created. Authentication is by API key.
The MailerCheck toolbox
9 tools: 5 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Credit BalanceReturn the current MailerCheck verification-credit balance.
- ReadGet Current AccountReturn the connected MailerCheck user and account identity.
- ReadGet Verification ListReturn one verification list, including its status, item count, verification timing, and aggregate result statistics.
- ReadList Verification ListsReturn one page of verification lists for the connected MailerCheck account, with an opaque cursor when another provider-controlled page exists.
- ReadList Verification ResultsReturn one page of email-level results for a verification list, optionally filtered by classification.
- WriteCreate Verification ListCreate a MailerCheck verification list by ingesting a name and email-address array. Approval by default
- WriteDelete Verification ListPermanently and irreversibly delete a MailerCheck verification list by ID. Approval by default
- WriteStart List VerificationIrreversibly start verification of every address in a MailerCheck list. Approval by default
- WriteVerify EmailConsumes exactly one MailerCheck verification credit on every successful call. Approval by default
One prompt, start to finish
What a governed MailerCheck run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — create verification list, delete verification list, start list verification, verify email — is shown as a plan and requires approval by default, including the 3 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to MailerCheck — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut MailerCheck to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.