Reverse Phone Lookup — Name, Email & Location

Reverse Phone Lookup — Name, Email & Location ✅ No API Key

Enrich a phone number into a person — names, emails, other phone numbers, location, company and social profiles when available. Powered by the Neuralverge API. No API key or account required, and you pay per completed lookup — matched or not; a run that fails is never charged.

Ideal for lead enrichment, identity resolution, fraud checks and CRM hydration.

✨ Why this Actor

• 📱 Phone → person — resolve a number to names, emails, location and profiles in one call.
• 💸 One flat price, no run fee — $0.010 per row written, matched or not. A number we cannot resolve comes back as one no result row, billed like any other row; a failed run costs $0.00.
• 🔑 No API key or account — enrichment runs on the Neuralverge backend.
• ⚡ Real-time & structured — fresh data each run, ready for a spreadsheet, CRM or AI pipeline.

🔧 How it works

1. Provide a phone number — any format works. Spaces, dashes, dots and parentheses are removed and a leading + is kept, so +91 95879 24808 is sent as +919587924808.
2. Run the Actor. The lookup happens on the Neuralverge backend.
3. Get one dataset row per lookup — one flat record: the source phone plus the resolved fields. Export to CSV, JSON or Excel, or pull it over the Apify API.

If the number can't be resolved, the run still writes one explicit no result row that echoes your query — billed like any other row. A run that fails writes nothing and is free.

Input

One number per run.

Field	Type	Notes
phone	string	The phone number to enrich. Any format; digits are extracted automatically.

{
  "phone": "79670777820"
}

What you'll receive

Each dataset row is flat: the tidied phone you submitted, followed by every field of the Neuralverge result at the top level — full_names, gender, date_of_birth, emails, phones, locations (country / state / city), company, linkedin_profile, x_profile, telegram_username and operator. No wrapper block — the fields are the columns.

Nulls & empty values are normal. Only fields that resolve for the number are filled — e.g. company, linkedin_profile and operator are often null.

Example output (real run)

A real dataset row for a phone lookup, shown in full — every resolved field at the top level, ready to map onto spreadsheet columns. The human markdown summary and the service fields (session_id, total_points) are produced by the system but omitted from the dataset.

{
  "phone": "79670777820",
  "full_names": [
    "Дмитрий Крыканов",
    "Дмитрий"
  ],
  "gender": null,
  "date_of_birth": null,
  "emails": [
    "dmitry.krykanov@yandex.ru"
  ],
  "phones": [
    "79670777820"
  ],
  "locations": [
    {
      "country": null,
      "state": null,
      "city": "Москва"
    }
  ],
  "company": null,
  "linkedin_profile": null,
  "x_profile": null,
  "telegram_username": null,
  "operator": null
}

Genuine output from a live run — the number resolved to a name, an email and a city.

When nothing is found

A lookup that runs but matches nothing still returns a row, so a batch never silently loses an input:

Column	Value
phone	echoed back exactly as submitted
found	false
message	why nothing was returned

Filter these out with found != false (or drop rows where message is set). This row is billed as one result — see Pricing.

Pricing

Pay per event — $0.010 per match ($10 per 1,000) written to the dataset. There is no run fee and no start fee.

Event	Price	Charged
Actor start	free	never
Failed run — invalid input, API error, timeout	free	never
Row written to the dataset	$0.010 ($10 / 1,000)	every row, including the "no result" row

A completed lookup is billed as one match, matched or not. When the source returns nothing, the Actor writes one explicit no-result row — the query you submitted plus found: false and a message explaining it — and that row is charged at the normal per-match price. A run that fails (missing input, bad key, upstream error) writes no row and costs $0.00.

Pricing is on top of your Apify platform usage.

Rate limit

There is a ceiling on how fast one Apify account can pull from the Neuralverge backend: 10 requests per second for this Actor, counted separately from the other Neuralverge Actors. One run is normally one request, so this is about how many runs you start at once, not about the size of a single run — at typical run times that is dozens of runs in flight at once, which is well above ordinary use.

Updated August 2026: this ceiling was doubled from 5 to 10 requests per second. Bulk jobs that used to hit 429s now go through.

Above the ceiling the backend answers HTTP 429. The Actor waits out the Retry-After it asks for and retries a few times before giving up; a run that does give up writes no row and is not charged.

If you need a higher rate for a bulk job, get in touch.

Free plan limits

Users on any paid Apify plan are not affected by anything in this section.

On the Apify Free plan this Actor may be started 5 time(s) per calendar month per user. A run that finds nothing still counts, because the lookup is performed either way. Every Neuralverge Actor carries its own allowance — running one never uses up another's. When a limit is reached the Actor stops gracefully with a status message naming it; everything resets on the 1st of every month, and any paid Apify plan removes all of it.

Integrations & API

Results are stored in a standard Apify dataset — export as CSV, JSON, XML or Excel, or fetch on demand through the Apify API. The Actor also plugs into Apify's integrations (Make, Zapier, n8n, webhooks) and can be called from any MCP client.

FAQ

Do I need an account or API key? No. Enrichment runs on the Neuralverge backend.

What phone format should I use? Any — spaces, dashes, dots and parentheses are removed and a leading + is kept. Do include the country code: the same number with and without it can match different records.

Am I charged if a number isn't matched? Yes — a lookup that ran is billed as one result ($0.010) even when it matched nothing; you get a no result row that says so. A run that fails — missing or malformed input, a bad key, an upstream error or timeout — is not charged.

---

Disclaimer: This Actor is an independent tool. Use enriched personal data in compliance with applicable privacy laws (e.g. GDPR) and only where you have a lawful basis.