Why agents make bad lists faster
A person who finds a lead usually has some sign the address is real. An agent often does not. It may guess a pattern such as first.last@company.com, take an address from a scraped page, or reuse a stale record, and then act on it at machine speed. One wrong guess is a bounce. A thousand of them in an hour is a reputation problem.
The agent also cannot judge risk the way you can. It does not know that a catch-all domain accepts every address, or that info@ rarely replies. Without a check, it treats every address the same, which is exactly what you do not want.
Put verification in the tool, not the prompt
A prompt that says "only send to valid emails" is a request, not a control. The agent can ignore it, misread it or run out of context. A gate in code is different: make verification a tool the agent must call, and make the send step refuse any address that has not passed.
That means two pieces. A verify function that returns a clear status, and a send function that checks the stored result before it does anything. Keep the check in the send step so there is no path to a message that skips it.
async function verify(email) {
const res = await fetch(`https://app.veridock.io/v1/verify?email=${encodeURIComponent(email)}`, {
headers: { Authorization: `Bearer ${process.env.VERIDOCK_API_KEY}` },
signal: AbortSignal.timeout(10_000),
});
if (!res.ok) throw new Error(`verify failed: ${res.status}`);
return res.json(); // { status, reason, score, suggestion }
}
export async function sendIfSafe(email, message, send) {
const { status, reason } = await verify(email);
if (status === "deliverable") return send(email, message);
if (status === "risky") return { queued: "review", reason }; // human or separate batch
return { skipped: status, reason }; // undeliverable or unknown: do not send
}Or let the agent call an MCP server
The Model Context Protocol lets an AI assistant call tools directly. VeriDock runs a hosted MCP server at https://veridock.io/api/mcp with two tools: verify_email for one address and verify_batch for up to 50 addresses in one call. It authenticates with your VeriDock API key, and each result carries a status, a reason code, a 0 to 100 score and a typo suggestion when there is one.
This is useful for an assistant that researches leads interactively, such as in Claude or Cursor, because it can check an address in the same step it finds it. It does not replace the send gate above. Treat the MCP tool as the way the agent learns the status, and keep the rule that decides what to do with it in your own code.
Give each agent its own API key. A separate key lets you cap its usage, revoke it without touching anything else, and see exactly what it checked.
Rules to give the agent
Whatever tool the agent uses, the routing rules are the same, and they should live in code or in a fixed policy, not in free text the model can reinterpret. Keep them short so they are easy to audit.
- Send only to deliverable addresses.
- Send risky addresses, such as catch-all and role addresses, only to a separate small batch or a human review.
- Never retry an undeliverable address, from any mailbox.
- Retry unknown addresses later instead of guessing. VeriDock does not bill unknown results.
- Stop the run if bounces pass a limit you set in advance, and suppress every hard bounce permanently.
Keep it cheap and observable
Verification is one credit per address that returns deliverable, undeliverable or risky, and repeat checks of the same address within 30 days are free from cache, so an agent that re-checks a lead does not pay twice. Use a test key (vd_test_) while you develop, because test keys never use credits.
Log every decision with the status and reason. When an agent runs unattended, that log is how you find out why a lead was skipped or why a batch was held, and it is the first thing to read if bounces spike.
Key takeaways
0/5Try it on a real address
Run syntax, DNS, MX, disposable, and role checks on any address. No signup needed.
Enter an address and press Check.
Runs real syntax, DNS and mail-server checks.
This demo checks syntax, domain, mail server, disposable and role-address rules. Sign up free for live mailbox checks.
Frequently asked questions
Verify addresses with one API call.
250 free checks to start, no card required. Unknown results are never billed.