Verify addresses, track list jobs, and upload bulk lists for checking
Connect EmailListVerify and ask about any address or list from the terminal. Check whether a single address is deliverable, pull detailed metadata like MX server and role detection, see how much credit is left, and follow a bulk job while it runs. Uploading a new list for verification is an approved step, previewed before it goes.
12 tools: 10 read, 2 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Emaillistverify run looks like inside Luumen.
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as delete maillist, upload email list. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
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 Emaillistverify — 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.
Connect in minutes. Every action scoped, approved, and audited from day one.