Email verification and validation API for your agent. One call per address.
The short answer
The short answer
Email verification API for an agent: it sends an email address to a catalog endpoint and reads deliverability status, catch-all flag and mail provider back. Several providers sell the call, so the agent tries the cheapest first. You pay per call, and a failed call costs nothing.
Updated
- Deliverability status
- Catch-all flag
- Mail provider
- Confidence score
- Typo suggestion
The job
What the Email verification API gives your agent
A verifier answers one question before you send: will this address bounce. Your agent sends the address, the provider checks the syntax, the mail server and the mailbox, and a status comes back. Several providers sell this check, and they do not return the same fields.
The part that matters most is the catch-all flag. Some domains accept mail for any name, so a clean check proves little. Most providers here report it, and a few add a confidence score or a typo suggestion, so your agent can fix jane.doe@exmaple.com before it spends anything else.
You give
an email address
jane.doe@example.com
You get
- Deliverability status
- Catch-all flag
- Mail provider
- Confidence score
- Typo suggestion
Email checker API
An email checker API is the same call under another name, and so is an email validation API. Your agent sends one address and reads a status back, such as valid, invalid, catch-all or unknown. Some providers add a score or a typo suggestion, so the agent can fix the address and check it again.
Bulk email verification
Each call checks one address, so bulk verification is your agent looping over the list. Ask it for the total before it starts: the price per check is on this page and on each endpoint page, and nothing is charged until a call runs.
Sort the results into three groups: valid, catch-all and the rest. Send to the valid group, decide per campaign on catch-all, and drop the rest.
Providers, cheapest first
What actually differs between providers
Today the price runs from $0.0019 to $0.0198 across 6 endpoints. The dearest costs about 10 times the cheapest. Price is only one difference. Each entry below says what that endpoint takes or returns that the others do not.
Icypeas$0.0019 / callWaits up to 60 seconds and returns FOUND or NOT_FOUND with a certainty and the MX details, with catch-all detection.
icypeas-email-verifyLeadMagic
$0.00495 / callReturns an email status and the catch-all flag, plus company name, industry and size when it knows the domain.
leadmagic-email-verifyTomba
$0.0089 / callReturns status, result, score, accept_all, MX and SMTP checks, and the pages where the address was seen.
tomba-email-verifier
ZeroBounce$0.0100 / callAdds a did_you_mean typo suggestion, a free-mailbox flag and the age of the domain.
zerobounce-validate
Hunter$0.01225 / callScores the address from 0 to 100 and lists the checks behind it, such as disposable, webmail, gibberish and SMTP.
hunter-email-verifier
Findymail$0.0198 / callReturns verified as true or false with the mail provider, and uses one verifier credit on every attempt.
findymail-api-verify- Any Site APIprice on request
Checks syntax, MX and mailbox, or returns a verdict already on file.
anysite-api-emails-verify
Cost
What 100 Email verification runs cost
$0.1900
100 addresses cost about $0.1900 through the cheapest endpoint, at Icypeas, and about $1.98 through the dearest. Each run is one call.
Sample calls
The request and what comes back
Each run is one POST to /v1/runs with an endpoint id and an input. These are illustrative calls with generic values. The run's result holds the provider's own fields.
{"endpointId":"icypeas-email-verify","input":{"email":"jane.doe@example.com"},"wait":30}// POST /v1/runs, then read run.status and run.result // result: waits up to 60 seconds and returns FOUND or NOT_FOUND with a certainty and the MX details, with catch-all detection
The prompt
Copy one prompt, give it to your agent.
Edit the names and numbers, paste it, and the agent runs the job and shows the cost.
- One run is one address.
- 1 step across 7 providers.
- Runs on demand, whenever you ask.
set up looot for Email verification API - https://looot.ai/use-cases/email-verification-api/skill.mdBefore you start
Settle these before the first run
- Verify the address you plan to send to, not the one you guessed. A found address that was never verified is the usual cause of a bounce.
- Treat catch-all as its own result. Keep those rows apart and decide per campaign whether to send.
- Run the cheap check on the whole list first. Spend more only on rows the first provider could not settle.
FAQ
Questions people ask
More ways to run this job
- use case
- Email verification API
- run
- address
- schedule
- on demand
- step
- Verify the address: icypeas leadmagic tomba hunter zerobounce findymail anysite
- setup
- https://looot.ai/use-cases/email-verification-api/skill.md
- llms.txt
- https://looot.ai/llms.txt
- updated
- 2026-10-04
Try Email verification with your own agent.
Start your workspace, top up, and paste the prompt into the agent you already use.