Email Tools Verify API
Verify an email address for deliverability: a status verdict (good, risky, or bad) with domain, mailbox, catch-all, disposable, and role signals plus a confidence score. Malformed addresses are rejected by the input schema with no charge; every syntactically valid address returns a billed verdict, including undeliverable ones.
$6.60/1k req, pay per request, no subscription.
{"email": "marcus.reyes@brightlanegoods.com","status": "good","score": 97,"domain": "brightlanegoods.com","free": false,"role": false,"disposable": false,"catchAll": false,... 3 more fields}
Pricing and providers
Email Tools Verify API pricing: one API, 2 interchangeable providers
The cheapest provider serves first. If it fails, the next one takes over in the same call.
Try it
Get Email Tools verify in one request
This sample shows 13 of 15 fields. See every field
{
"found": true,
"data": {
"items": [
{
"email": "marcus.reyes@brightlanegoods.com",
"status": "good",
"score": 97,
"domain": "brightlanegoods.com",
"free": false,
"role": false,
"disposable": false,
"catchAll": false,
"mxRecords": [
"aspmx.l.google.com",
"alt1.aspmx.l.google.com"
],
"mxProvider": "Google Workspace"
}
]
}
}Full parameter and response reference - every field, type, and example for this endpoint.
Reference
One request, one response shape.
Every field you send and every field you get back, each with a real example.
Last verified 2026-10-31 · uptime and latency measured over 30d
Request body
JSON, posted to this endpoint.
- emailstring
marcus.reyes@brightlanegoods.com
The email address to verify (e.g. jane.doe@acme.com). Exactly one @, a dotted domain, no whitespace or angle brackets. Addresses on reserved, never-deliverable TLDs (.invalid, .test, .example, .localhost, .local, .internal, .blink) and HTML/JSON escape artifacts (a u003e prefix) are rejected locally with no charge.
- requireFieldsarray
Optional; omit it and routing is unchanged, with the cheapest source serving. Name the output fields this request must be able to return, for example `reason`, and it is served only by a source that returns every one of them. Fields you do not name are still returned whenever the serving source has them. This can raise your price: when the cheapest source cannot return a named field, a dearer source serves, and you are quoted and charged its price. A named field can still be absent on a result that genuinely lacks it. Naming a combination that no single source returns together is refused as invalid input, with no charge.
Response
JSON, one example value per field.
Verification records: the email address with its deliverability verdict and the domain, mailbox, and reputation signals behind it. A record is returned for every syntactically valid address, including ones the verdict marks undeliverable. Populated whenever the provider has data for the entity.
- catchAllboolean
false
Domain accepts all addresses.
- disposableboolean
false
- domainstring
brightlanegoods.com
- emailstring
marcus.reyes@brightlanegoods.com
Populated whenever the provider has data for the entity.
- freeboolean
false
Free email provider.
- mxProviderstringcan require
Google Workspace
Mail provider behind the address domain, e.g. Google. Null when the serving source does not report one.
- mxRecordsstring[]
MX record hosts published by the address domain.
- reasonstringcan require
Why the verdict was reached. Published by only one of the two sources, so it is absent on most calls; never treat it as required.
- roleboolean
false
Role-based address (e.g. info@).
- scoreinteger
97
Confidence in the verdict, 0-100. Coarse rather than graded on most calls: it tracks the status rather than ranking addresses within one.
- statusstring
good
Deliverability verdict: good (the mailbox accepted), bad (it was refused), or risky (no source could settle it - usually a catch-all domain that accepts every address, sometimes a receiving server that declined to answer at all). Populated whenever the provider has data for the entity.
- foundboolean
true
- reason"not_found"can require
Present only when `found` is false, and says why there is no result. `not_found`: the source states the target does not exist, or returned nothing for it. A `found: false` answer is a successful call, not an error, and `costUsd` is what it actually cost.
FAQ
About the Email Tools Verify API
The AnyAPI Email Tools Verify API returns Email Tools verify data as normalized JSON from one POST call to /v1/run/email.verify. Verify an email address for deliverability: a status verdict (good, risky, or bad) with domain, mailbox, catch-all, disposable, and role signals plus a confidence score. Malformed addresses are rejected by the input schema with no charge; every syntactically valid address returns a billed verdict, including undeliverable ones. AnyAPI routes each request across 2 sources and falls back automatically when one fails. It costs from $6.60 per 1,000 requests, in US dollars with no subscription and no monthly minimum. Over the last 30 days, 100.0% of Email Tools verify calls through AnyAPI succeeded, with a median response time of 4.9 seconds across 31,411 measured calls.