Find a mobile phone number
/people/find-mobileFind a mobile phone number for a person. LinkedIn URL is the strongest identifier. Waterfalls across providers that expose mobile data, cheapest-first.
Call it over REST
Authenticate with a bearer token against https://api.agntdata.dev. Swap the placeholders for your key and parameter values.
curl -s -X POST "https://api.agntdata.dev/people/find-mobile" \
-H "Authorization: Bearer <YOUR_AGNTDATA_API_KEY>" \
-H "Content-Type: application/json" \
-d '{ "identifiers": {} }'Copy-paste prompt
Paste this into a coding agent. It connects the superagnt MCP server, finds the tool data_agnt_people_find_mobile, and runs a first call — with the REST fallback if MCP is unavailable.
You are wiring up the agntdata "Lead APIs" API to use this endpoint: Find a mobile phone number.
1. CONNECT over MCP (preferred). Add the superagnt MCP server, then let the client
run OAuth on first tool call — no token to paste:
claude mcp add --scope user --transport http superagnt https://mcp.superagnt.com/mcp
claude mcp login superagnt
MCP endpoint: https://mcp.superagnt.com/mcp
After connecting, the tool you want is named exactly:
data_agnt_people_find_mobile
Call agnt_tools_search or agnt_tools_list_enabled to confirm it is available.
2. REST fallback (if you are not using MCP):
POST https://api.agntdata.dev/people/find-mobile
Header: Authorization: Bearer <YOUR_AGNTDATA_API_KEY>
Required parameters:
- identifiers (object, required) — Unique handles used to resolve the person. Provide AT LEAST ONE of `email` or `linkedin_url`. Name + company are NOT accepted — call `/people/email-finder` first if that is all you have.
Optional parameters:
- max_cost_cents (number, optional)
3. COST & KEY. This endpoint is priced per call in credits, and each successful response reports its own cost in its meta.costCents field. Only successful calls are charged.
Get an agntdata API key at https://app.agntdata.dev.
4. TEST. Connect the server (or set the key), discover the tool
(data_agnt_people_find_mobile), run one minimal call with just the required parameters,
and report back the shape of the JSON response (top-level fields).
Reference (machine-readable variant): https://superagnt.com/docs/apis/lead/agnt/endpoints/people_find_mobile.md{
"name": "people_find_mobile",
"description": "Find a mobile phone number for a person. REQUIRES a `identifiers` object containing ONLY `email` and/or `linkedin_url`. `first_name`/`last_name`/`domain` are NOT accepted — if you only have a name + company, call `/people/email-finder` first. `linkedin_url` is the strongest signal. agntdata waterfalls across providers that expose mobile data, cheapest-first, until a number is found or your budget is exhausted.",
"parameters": {
"type": "object",
"properties": {
"identifiers": {
"type": "object",
"properties": {
"email": {
"type": "string",
"format": "email",
"description": "Work or personal email address."
},
"linkedin_url": {
"type": "string",
"format": "uri",
"description": "Full LinkedIn profile URL — strongest signal for mobile lookups."
}
},
"additionalProperties": false,
"description": "Unique handles used to resolve the person. Provide AT LEAST ONE of `email` or `linkedin_url`. Name + company are NOT accepted — call `/people/email-finder` first if that is all you have."
},
"max_cost_cents": {
"type": "number",
"minimum": 0
}
},
"required": [
"identifiers"
]
}
}| Name | In | Type | Required | Description |
|---|---|---|---|---|
identifiers | body | object | required | Unique handles used to resolve the person. Provide AT LEAST ONE of `email` or `linkedin_url`. Name + company are NOT accepted — call `/people/email-finder` first if that is all you have. |
max_cost_cents | body | number | optional |
Mobile lookup result.
{
"type": "object",
"required": [
"success",
"data"
],
"properties": {
"success": {
"type": "boolean",
"enum": [
true
]
},
"data": {
"$ref": "#/components/schemas/PeopleFindMobileResponse"
},
"meta": {
"$ref": "#/components/schemas/AgntMeta"
}
}
}This endpoint is priced per call and deducted from your agntdata balance; only a successful call is billed. Every billable response reports its own cost in meta.costCents.
Get a key at app.agntdata.dev.
start calling
Point your client at https://mcp.superagnt.com/mcp and your agent has this endpoint, plus every other source on one balance.