Email Validation API — Deliverability Check, 1 Point
Bad addresses cost more than the send. Bounces damage your sending reputation, and reputation damage lands on every message you send afterwards, including the ones to people who wanted to hear from you.
{
"session_id": "1c93…",
"kind": "email_validation",
"email": "jane.doe@acme.com",
"human": "Address looks deliverable.",
"machine": {
"email": "jane.doe@acme.com",
"result": "valid",
"message": "…",
"isCatchAll": false,
"provider": "google_workspace",
"confidence": "high"
},
"total_points": 1
}- You send
- One email address
- You get back
- The verdict, catch-all flag, mail provider and confidence
- Coverage
- Global.
- Price
- 1 pts — $1 per 1,000
- 1 point per check — the cheapest call in the catalog.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Sending and seeing what bounces | None up front | Your sending reputation | The damage lands on every future message, not just the bad ones |
| A dedicated verification service | Another vendor, another key, usually a bulk upload flow | Per-address credits, often with a minimum | Batch-oriented, so it sits awkwardly in a real-time signup flow |
| NeuralVerge | One request, same key as every other source | $1 per 1,000 | A catch-all domain limits what any validator can tell you — that is a property of the domain, not the check |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
email | string | The address that was checked. |
result | string | The verdict for the address. |
message | string | Explanation of the verdict. |
isCatchAll | boolean | Whether the domain accepts mail to any address, which limits what a check can prove. |
provider | string | The mail provider behind the domain. |
confidence | string | How strongly the verdict is supported. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
Cheap enough to call inline on a signup form. Check `isCatchAll` alongside `result` — on a catch-all domain a positive verdict proves less than it appears to.
curl -X POST https://api.neuralverge.ai/functions/v1/run-email-validation \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "email": "jane.doe@acme.com" }'What teams use it for
Where this field shows up in an actual workflow.
Filter a list before a campaign instead of learning from the bounce report.
Catch typos and disposable addresses at the moment someone registers.
Find the addresses that have gone stale since you collected them.
Run it after Email finder so a guess never becomes a send.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
Global.
Checked at request time.
An address on its own is still personal data. Handle it under your own lawful basis and honour opt-outs.
- —On a catch-all domain no validator can confirm a specific mailbox exists — the flag tells you when you are in that situation.
- —A valid verdict describes the address now, not next quarter.
- —It checks deliverability, not whether the person still works there.
Questions, answered
The domain is configured to accept mail sent to any address at it. That means a check cannot prove a specific mailbox exists, so a positive result on a catch-all domain should be treated as weaker evidence.
Related sources
Try email validation on your own data
One request format across every source in the catalog.