Reverse Email Lookup API — Name, Company & Phone
Give NeuralVerge an email address and it returns the person it belongs to: every name they are known by, current company and position, location, alternate emails and phone numbers, and linked social profiles where they exist. One request, structured JSON, no vendor waterfall to assemble yourself.
{
"session_id": "8b21…",
"kind": "email_enrichment",
"email": "jane.doe@acme.com",
"human": "Jane Doe is VP of Sales at Acme…",
"machine": {
"full_names": ["Jane Doe", "Jane A. Doe"],
"gender": "female",
"emails": ["jane.doe@acme.com", "j.doe@acme.com"],
"phones": ["+15125550143"],
"locations": [
{ "country": "US", "state": "TX", "city": "Austin" }
],
"company": "Acme Technologies",
"position": "VP of Sales",
"linkedin_profile": "https://linkedin.com/in/example",
"x_profile": "https://x.com/example"
},
"total_points": 10
}- You send
- One email address
- You get back
- The resolved person: identity, employment, location and contacts
- Coverage
- Global, with the highest hit rate on business email addresses.
- Price
- 10 pts — $10 per 1,000
- Charged only on a match. Addresses that resolve to nobody are not billed, so a low-quality list costs you nothing but time.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Looking them up by hand | Search the address, check social profiles, cross-reference | Free, five to ten minutes each | Fine for a handful, impossible for a list, and the output is not structured |
| Stitching several vendors together | Contracts and keys with two or three providers, plus your own fallback logic | Several subscriptions | You maintain the waterfall order, the deduplication and the field mapping |
| NeuralVerge | One request | $10 per 1,000, misses not billed | Not every address resolves — business addresses have much the highest hit rate |
What you get back
Every field in the response shown above.
| Field | Type | Description |
|---|---|---|
full_names | array | Every name variant known for the person. |
gender | string | Gender where it can be determined. |
date_of_birth | string | Where it is known; often empty. |
emails | array | All known addresses for the person, not only the one you sent. |
phones | array | Known phone numbers, when any are found. |
locations | array | Country, state and city. |
company | string | Current employer. |
position | string | Current job title. |
linkedin_profile | string | Professional profile URL where one is linked. |
linkedin | object | Company name, title and profile URL as held on that profile. |
x_profile | string | X profile where one is linked. |
telegram_username | string | Telegram handle where one is linked. |
How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
One address per request, which keeps the call cheap to retry and easy to wire into a signup hook. Every response carries a session id, a readable human summary and total_points alongside the structured machine object.
curl -X POST https://api.neuralverge.ai/functions/v1/run-email-enrichment \
-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.
Turn a bare work email into a named, titled, routable lead before it hits the queue.
Resolve a spreadsheet of addresses into people with roles and companies.
Fill in the title, employer and profile links the original form never asked for.
Let an agent resolve a person from a single identifier mid-task, without a research detour.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
Global, with the highest hit rate on business email addresses.
Resolved at request time rather than served from a static file.
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.
- —Personal addresses resolve far less often than work addresses.
- —Role addresses such as info@ or support@ belong to a mailbox rather than a person and will usually not resolve.
- —Phone numbers come back for a subset of matches only, and this source does not return carrier or line-type data — Phone enrichment US does.
Questions, answered
It is the lookup that starts from an email address and returns the person behind it — their name, where they work, what they do there, and their other public contact points. The name distinguishes it from an ordinary email search, which goes the other way.
Related sources
Try email enrichment on your own data
One request format across every source in the catalog.