Email Finder API — Find a Work Email by Name & Domain
You know who you want to reach and where they work. This source takes a first name, a last name and a company domain, and returns the work email address, with a confidence rating and the provider that resolved it.
{
"session_id": "5a70…",
"kind": "email_finder",
"domain": "acme.com",
"first_name": "Jane",
"last_name": "Doe",
"human": "Found jane.doe@acme.com with high confidence.",
"machine": {
"firstName": "Jane",
"lastName": "Doe",
"domain": "acme.com",
"found": true,
"email": "jane.doe@acme.com",
"confidence": "high",
"provider": "…"
},
"total_points": 10
}- You send
- First name, last name and a company domain
- You get back
- The work email address with a confidence rating
- Coverage
- Global, strongest on companies with their own mail domain.
- Price
- 10 pts — $10 per 1,000
- Charged only when an address is found. A miss costs nothing, so a long list is safe to run.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Guessing the pattern | Work out the company's format and construct the address | Free | Patterns vary within one company, and a wrong guess costs you sender reputation |
| A dedicated finder tool | Another subscription and another seat to manage | Monthly per seat or per credit | Usually a separate silo from the rest of your data pipeline |
| NeuralVerge | One request, same key and format as every other source | $10 per 1,000, misses not billed | Not every person resolves — small companies and generic domains are hardest |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
firstName | string | The first name you sent. |
lastName | string | The last name you sent. |
domain | string | The company domain you sent. |
found | boolean | Whether an address was resolved — branch on this. |
email | string | The resolved work email address. |
confidence | string | How strongly the address is corroborated. |
provider | string | Which upstream resolved the address. |
message | string | Explanatory note, present when there is something to say. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
All three parameters are required. The `found` boolean in the response is the field to branch on, rather than testing whether `email` is empty.
curl -X POST https://api.neuralverge.ai/functions/v1/run-email-finder \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"domain": "acme.com",
"first_name": "Jane",
"last_name": "Doe"
}'What teams use it for
Where this field shows up in an actual workflow.
Turn a list of names and companies into addresses you can actually send to.
Recover addresses for contacts that came in without one.
You found the right person on a company page; this gets you the way to reach them.
Let an agent resolve the address as a step rather than as a separate tool.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
Global, strongest on companies with their own mail domain.
Resolved at request time.
This source returns personal data. Use it for legitimate business purposes under your own lawful basis, honour deletion and opt-out requests, and check the acceptable use policy for what is out of bounds.
- —Generic mailbox providers are not company domains and will not resolve a specific person.
- —Very small companies often have no discoverable pattern at all.
- —A high confidence rating is a strong signal, not a delivery guarantee — validate before a large send.
Questions, answered
Opposite directions. The finder goes from a person and a company to an address. Reverse email lookup goes from an address to the person behind it.
Related sources
Try email finder on your own data
One request format across every source in the catalog.