15 tools do this job
Email verification API: is this address deliverable, before you send
Hand your agent an address and get back a verdict: deliverable, undeliverable, or the third bucket every verifier has and each one names differently. 15 tools do this through 鹦鹉AI, and what separates them is not accuracy claims. It is what they charge for an answer of “unknown”, which on a real B2B list is about a fifth of it.
Billed per call, for what you use. No card required.
15 of the 15 tools that answer this job are live-verified against their upstream.
Try it
What is the best way to ask 鹦鹉AI?
1 · Set your agent up, once
in your agent's chat
set up 鹦鹉AI — https://parrot.amorist.cn/llms.txt
2 · Then ask for the job
the prompt
Using 鹦鹉AI, verify these 40 addresses before I send. Show me the price first, then give me three lists: safe to send, do not send, and unknown with the reason.
Why this prompt works
Verify in one batch
One list in, one table out. Cheaper to reason about than 40 calls.
Ask for three buckets
Valid and invalid are easy. The third bucket is the decision you have to make.
Ask what a miss costs
One tool charges nothing for “unknown”. The others bill it as a check.
Verify close to the send
Data decays. A check from three weeks ago is not a check.
Why 鹦鹉AI
Why go through 鹦鹉AI
No subscription, no seats
Charged per call. No card, no minimum; top up the prepaid balance.
Switch by changing a word
Another tool is a different word in the prompt, not a new integration.
From the field
What people actually struggle with
Verification is the step everybody agrees on and nobody is happy with. From ~150 Reddit and X posts in August 2026, after excluding four separate astroturf clusters, these are the complaints that recur.
Catch-all domains are a fifth of the list and nobody knows what to do with them
“Catch-all domains are about 20% of any B2B list. Most operators throw them away because the bounce risk is real”
@DeanFiacco on X
What this page can do about it:No tool resolves a true catch-all. What differs is what each one hands back: a distinct status, a probability, or a shrug. Each tool's third bucket has its own name, so decide once instead of per list.
An unknown result is the server refusing to answer, not the tool failing
“So the verifier returns unknown, or accept-all, or risky depending on the wording. That is not the tool failing.”
r/ColdEmailAndSales
What this page can do about it:Exactly right, and it is why “which verifier is most accurate” is the wrong question. Ask instead who charges you for the shrug: one of these five does not.
Role addresses and catch-alls get misclassified
“also curious if anyone has had issues with verification tools missing role accounts or catch alls. thats been my biggest frustration.”
r/Coldemailing
What this page can do about it:Hunter reports role and disposable addresses as their own statuses; the others fold them in. Whether a role address is worth keeping is genuinely unsettled, so the honest answer is to keep them separate and decide per campaign.
Doing it yourself gets your IP blocked
“SMTP probing gets your IP blocklisted and the big providers accept everything anyway.”
@kumard_3 on X
What this page can do about it:Both halves are true. Cloud providers block port 25 and repeated probes from one address get you listed, which is what you are paying a tool's IP pool for. It also explains why the unknown bucket exists at all.
The detail
What actually differs
Every tool names the third bucket differently.
Hunter returns accept_all, webmail, disposable and unknown as separate statuses with a score; LeadMagic returns a plain is_domain_catch_all flag plus the MX provider; Icypeas returns a certainty level. Compare the buckets, not the headline accuracy number.
Icypeas is asynchronous: you submit the address and read the verdict from a second call.
The other four answer in the same request, which matters when an agent is verifying a list interactively.
Background
What does an email verification API actually do?
It resolves the domain's MX records and opens an SMTP conversation with the receiving server to ask whether the mailbox exists, without delivering a message. Three answers come back: the server confirms, the server denies, or the server accepts everything and tells you nothing. That last case is a catch-all domain, and no tool can resolve it, because the information does not exist on the wire.
Questions
Before you start
Does verification stop bounces?
It removes the addresses that are provably dead, which is most of the risk. It cannot catch an address that goes stale between the check and the send, or one that a security gateway rejects at delivery time. Verify close to the send, not weeks before.
What is a catch-all or accept-all domain?
A domain whose server accepts mail for every address without saying whether the mailbox exists. No verifier can resolve it. Expect roughly a fifth of a B2B list to land there.
How much does verification cost here?
Under one credit per check at its own rate. One tool charges nothing for an inconclusive result; the others bill it as a check.
Can I run several verifiers over the same list?
Yes, they are all callable from the same catalog, and heavy senders do exactly that because verifiers disagree on the ambiguous rows. Your agent chains them; 鹦鹉AI compares the options but does not route or fail over on its own.
Related
Other jobs your agent can do
Run the full sequence
Workflows that use this job