Invalid Bounce
for LuumenAI
Start bulk email verification jobs from the terminal, as approved steps.
Hand Luumen a list of addresses and it starts a bulk verification job in Invalid Bounce with INVALID_BOUNCE_START_BULK_VERIFICATION. The job is asynchronous and consumes the connected account's verification quota, so the call is previewed, approved by default, and written to the audit log before it runs. Connects with an API key.
The Invalid Bounce toolbox
1 tools: 0 read, 1 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- WriteStart Bulk Email VerificationIrreversibly start an asynchronous email-verification job using the connected account's verification quota. Approval by default
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 — start bulk email verification — is shown as a plan and requires approval by default, including the 1 action 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 Invalid Bounce — 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 Invalid Bounce to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.