Phone Finder API and MCP — Phone Numbers from a LinkedIn Profile
Send a LinkedIn profile URL and this source returns the phone numbers it can find for that person, with the carrier for each, their personal email, name, company, position and location.
- You send
- A LinkedIn profile URL
- You get back
- Phone numbers with carrier and owner names, plus personal email, name, company, position and location
- Coverage
- People with a LinkedIn profile.
- Price
- 150 points, only when a phone is found — $150 per 1,000
- Charged only when a phone is found. A profile with no matching number is not billed.
Ways to get this data
Three approaches teams use today, and where each one runs into trouble.
| Approach | What it takes | Cost | Trade-off |
|---|---|---|---|
| Asking or searching by hand | Look through signatures, websites and directories | Free, and slow | Rarely turns up a direct number, and nothing checks that it is theirs |
| A contact-data platform | A seat licence and phone credits | Per seat plus per credit | Credits can go on numbers you can't use |
| NeuralVerge | One request per profile | $150 per 1,000, only on a found phone | Many profiles have no findable number — those lookups cost nothing |
What you get back
Every field in the example response below.
| Field | Type | Description |
|---|---|---|
machine.found | boolean | Whether a matching phone was found. |
machine.phones | array | The phone numbers found, in international format. |
machine.phone_details | array | Per number: phone, owner_names and carrier. |
machine.personal_email | string | Personal email address, returned only when a phone is found. |
machine.full_name | string | The person's name. |
machine.company | string | Current company. |
machine.position | string | Current position. |
machine.locations | array | Country, state and city. |
Example response
A real response, as returned.
{
"session_id": "11111111-1111-1111-1111-111111111111",
"kind": "phone_finder",
"linkedin_url": "https://www.linkedin.com/in/john-doe/",
"human": "# Phone finder\n\n- **LinkedIn profile:** https://www.linkedin.com/in/john-doe/\n- **Personal email:** john.doe@example.com\n- **Phones:**\n - +12025550143",
"machine": {
"found": true,
"phones": ["+12025550143"],
"phone_details": [
{
"phone": "+12025550143",
"owner_names": ["John Doe"],
"carrier": "Verizon Wireless"
}
],
"personal_email": "john.doe@example.com",
"full_name": "John Doe",
"company": "Example Inc",
"position": "CEO",
"locations": [
{ "country": "United States", "state": "California", "city": "San Francisco" }
]
},
"total_points": 150
}How to run it
The same lookup works from the app, the API, or as a tool an agent can call mid-task.
This endpoint is synchronous: the call blocks until the lookup completes and returns the records directly. url is required and takes a LinkedIn profile URL. One person per request.
curl -X POST https://api.neuralverge.ai/functions/v1/run-phone-finder \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "url": "https://www.linkedin.com/in/john-doe/" }'What teams use it for
Where this field shows up in an actual workflow.
Add a direct number to the few accounts worth a phone call.
Reach a shortlisted candidate who doesn't answer messages.
Fill in the phone on a CRM contact you already have the profile for.
Check whether the number you hold matches the person's name.
Coverage, freshness and limits
What this source covers, how fresh it is, and where it stops.
People with a LinkedIn profile.
Looked up at request time.
This source returns personal contact data. Use it only for legitimate business purposes under your own lawful basis, follow the calling and messaging rules of each country you contact, honour opt-out and deletion requests, and check the acceptable use policy for what is out of bounds.
- —Many profiles have no findable number.
- —Numbers are matched on the owner's name, so people with very common names are harder to confirm.
- —The sample above is the documentation example with placeholder data, not a real person.
Questions, answered
Only when a phone is found — 150 points per found result. A lookup that finds no matching number is free.
Related sources
Try phone finder on your own data
One request format across every source in the catalog.