Use case, Mobile number finder

Mobile number finder API for your agent. One call per person.

Send a LinkedIn profile URL, an email, or a name and a company domain. Read phone number and line type back. Your agent picks the provider, and you pay per call.

Give this to your agent
set up looot for Mobile number finder API - https://looot.ai/use-cases/find-phone-numbers/skill.md

The short answer

The short answer

Mobile number finder API for an agent: it sends a LinkedIn profile URL, an email, or a name and a company domain to a catalog endpoint and reads phone number, line type and country code back. Several providers sell the call, so the agent tries the cheapest first. You pay per call, and a failed call costs nothing.

Updated

  • Phone number
  • Line type
  • Country code and format
  • Carrier
  • Match confidence

The job

What the Mobile number finder API gives your agent

A phone lookup starts from something you already know about a person, such as a LinkedIn profile or a work email, and returns a number. It is the most expensive lookup in the contact family, and the price spread across providers is wide.

That makes the order of attempts matter. Some providers return only a mobile number, some return every number they hold, and some return nothing for people in the EU. Your agent can ask the cheapest provider first and try the next one only when the first has no match.

You give

a LinkedIn profile URL, an email, or a name and a company domain

https://www.linkedin.com/in/jane-doe-example

You get

  • Phone number
  • Line type
  • Country code and format
  • Carrier
  • Match confidence

Providers, cheapest first

What actually differs between providers

Today the price runs from $0.0445 to $0.7500 across 6 endpoints. The dearest costs about 17 times the cheapest. Price is only one difference. Each entry below says what that endpoint takes or returns that the others do not.

  1. Tomba logoTomba

    Starts from an email, a LinkedIn URL or a domain, and returns international, local and E.164 formats with line type and carrier.

    tomba-phone-finder
    $0.0445 / call
  2. AI Ark logoAI Ark

    Takes a LinkedIn URL, or a name with a domain, and returns null data when no person or no phone is found.

    ai-ark-people-mobile-phone-finder
    $0.0539 / call
  3. LeadMagic logoLeadMagic

    Takes a profile URL, a work email or a personal email and returns the mobile number.

    leadmagic-people-mobile-finder
    $0.0990 / call
  4. Aviato logoAviato

    Takes one identifier, such as an email, a LinkedIn URL or a Crunchbase id, and returns phone numbers with a score.

    aviato-person-phone
    $0.1500 / call
  5. Findymail logoFindymail

    Takes a LinkedIn URL and returns the phone and its line type, with no result for EU citizens.

    findymail-api-search-phone
    $0.1980 / call
  6. Lusha logoLusha

    Takes a LinkedIn URL, an email, or a name with a domain, and is billed more when it finds a number than when it only matches the person.

    lusha-contacts-phone-find
    $0.7500 / result
  7. Any Site API

    Takes a LinkedIn URL and returns matches with a confidence level and how each was resolved.

    anysite-api-phones-find
    price on request

Cost

What 100 Mobile number finder runs cost

$4.45

100 people cost about $4.45 through the cheapest endpoint, at Tomba, and about $75.00 through the dearest. Each run is one call.

Sample calls

The request and what comes back

Each run is one POST to /v1/runs with an endpoint id and an input. These are illustrative calls with generic values. The run's result holds the provider's own fields.

Request
{"endpointId":"tomba-phone-finder","input":{"linkedin":"https://www.linkedin.com/in/jane-doe-example"},"wait":30}
ResponseSample output
// POST /v1/runs, then read run.status and run.result
// result: starts from an email, a LinkedIn URL or a domain, and returns international, local and E.164 formats with line type and carrier

The prompt

Copy one prompt, give it to your agent.

Edit the names and numbers, paste it, and the agent runs the job and shows the cost.

  • One run is one person.
  • 1 step across 7 providers.
  • Runs on demand, whenever you ask.
Prompt: Mobile number finder API
Use looot to find a direct phone number for https://www.linkedin.com/in/jane-doe-example and tell me whether it is a mobile or a landline. 1. Set up https://looot.ai/skill.md. 2. Search the catalog for each step and check its price before you call. 3. Run the cheapest endpoint that fits. 4. Show the results as a table and the total cost.

Give this to your agent
Setup command
set up looot for Mobile number finder API - https://looot.ai/use-cases/find-phone-numbers/skill.md

Before you start

Settle these before the first run

  • Know the region you call. One provider here returns no result for EU citizens for legal reasons, and others hold thinner data outside the US.
  • Respect do-not-call flags. One provider returns a doNotCall field, and your agent should keep it with the number.
  • A number that is found is billed. A lookup that matches nobody is often free, but the rules differ per provider, so read the endpoint page for the exact charge.
  • Misses are common. Many lookups return no number even after several providers, so plan for an empty answer and keep the rows that miss.

FAQ

Questions people ask

Send the profile URL to a phone-finder endpoint. Several providers here accept it. Use the vanity alias in the URL, not the numeric id. The answer is a number with a line type, or an empty result.

Yes. Some providers take an email in place of a profile. Your agent reads each endpoint's parameters first, because the accepted inputs differ.

Direct dials and mobiles are harder to source, so providers charge more for them. The live prices on this page show the spread, and the cheapest provider is not always the one with the best coverage.

The provider matched nobody, or matched the person and holds no number. Some providers bill the second case at a lower rate. Your agent reports it as a miss and can move on to the next provider.

Often. Misses are common for this job, also when your agent sends job:people.phone.find with fallback on and looot tries several providers in a row. Treat a number as a bonus on a row, not as something every row will get.

It cannot promise a number, and coverage of EU mobile numbers is thin: one provider returns nothing for EU citizens. It does not check whether a number you already hold is live; that is a carrier lookup, a different job.

You pay per call, and the price depends on the provider your agent picks. This page reads the cheapest live price from the catalog and shows no number when the catalog is unreachable.

No. A call that fails at the provider costs nothing, and your agent can retry it or send it to another provider.

No. One looot key reaches every provider in the catalog. You top up once, and each call is billed at the price shown before it runs.

Send a POST to /v1/runs with the endpoint id, the input and a new idempotency key, and your looot token in the Authorization header. With wait set to 30, the answer comes back in the response when the run ends within 30 seconds. Otherwise poll GET /v1/runs/<runId>.

That needs scheduled runs, not available yet. Run it by hand whenever you want fresh results.

No. looot bills per call, and nothing runs while your agent is idle.

More ways to run this job

For agents
use case
Mobile number finder API
run
person
schedule
on demand
step
Find the phone number: tomba ai-ark leadmagic aviato findymail lusha anysite
setup
https://looot.ai/use-cases/find-phone-numbers/skill.md
llms.txt
https://looot.ai/llms.txt
updated
2026-10-04

Try Mobile number finder with your own agent.

Start your workspace, top up, and paste the prompt into the agent you already use.