Find a direct mobileMatch the right personPay for found mobiles
Tool resultExample
Jordan ExampleVP Sales · Example Co
+1 (555) 014-2290Mobile
Call JordanRight person
Built for tools that answer
No mobile found? 0 credits
A selection of agent builders using Forager for mobile numbers · plus other teams on ForagerA selection of teams using Forager
For agent frameworks and builders
The job
Let people who build apps by prompting an AI app builder add lead search, contact enrichment or business-card capture without signing up for a data vendor themselves.
When
A user prompts the app builder for a CRM, lead-gen or networking app that needs real people and company data.
Outcome
Builders ship data-backed apps in days instead of wiring vendors themselves.
When to use it: A user prompts the app builder for a CRM, lead-gen or networking app that needs real people and company data.
Register an integration that wraps POST /person_role_search/, POST /person_detail_lookup/ and POST /organization_search/ with typed schemas
When generated code needs contacts, call /person_contacts_lookup/work_emails/ and POST /person_contacts_lookup/phone_numbers/ through the platform's metered key
For card or badge capture apps, OCR the name and company and resolve the person with POST /person_detail_lookup/
Bill builders in platform credits and show credits used per call
Inputs
Outputs
natural-language app prompt
person
name + company
company
company domain
work_email
phone_number
Lead recipe 2
Add Forager as a waterfall step in an agent's contact tool
When to use it: An agent's find-contact tool returns nothing for a third of prospects because its single source has no mobiles.
Show the steps
Define one find_contact tool in your framework that takes a LinkedIn URL or name and company
Inside it, call POST /person_contacts_lookup/phone_numbers/ then POST /person_contacts_lookup/work_emails/ when the earlier source returns nothing
Return a typed result with the field names, the source that found it and the person_id
Count credits per found result only, so a miss in the Forager step adds 0 to the run's cost
Who evaluates mobile numbers at agent frameworks and builders, and what they are judged on
Product manager who owns the enrichment feature: judged on what users see when they open a record
Engineering lead integrating the API: judged on response time and errors they can route on
Partnerships or data lead managing vendors: judged on cost per valid result
A selection of agent builders using Forager for mobile numbers · plus other teams on ForagerA selection of teams using Forager
Nooks
Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
Amplemarket
AI SDRs
Selected use case: mobile numbers inside its contact waterfall.
Clay
GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
Airscale
Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
Emergent Labs
Agent builders
AI app-building platform where agents design, code and deploy full-stack apps.
Orbital
Lead databases
Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.
BetterContact
Waterfall enrichment
Selected use case: a Forager step in its waterfall for mobile numbers.
HubSpot
CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
“Forager's great for accuracy, the numbers we get from them are consistently the highest grade for accuracy and confidence. They've earned our trust when connect rates matter most.”
OrbitalAaron JosephHead of BizOps
800M+people
65M+companies
How to test it
Test mobile numbers on your own sample
Pull a sample. Take profiles your users looked up last week.
Run it. Use a self-serve key, or book a demo and send us the list.
Measure what your users feel. Connect rate for mobiles, bounces for emails, and whether the right person answers.
How do AI agent builders use Forager mobile numbers?
⌄
Let people who build apps by prompting an AI app builder add lead search, contact enrichment or business-card capture without signing up for a data vendor themselves. Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. This page walks through 2 workflows with the exact steps.
What do mobile numbers cost for AI agent builders?
⌄
Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. That is $0.20 per mobile number on Starter month to month and $0.15 on Pro with yearly billing. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices
Why do AI agent builders add mobile numbers?
⌄
Typed people and contact lookups your agents can call, paid per result. Products like yours are judged on whether the agent reached the right person, which is why the cost that counts is per result that reaches the right person. Run your own sample to see what mobile numbers returns for your users before you build on it.
How do I add contact enrichment to a vibe coded app?
⌄
When generated code needs contacts, call /person_contacts_lookup/work_emails/ and POST /person_contacts_lookup/phone_numbers/ through the platform's metered key. For card or badge capture apps, OCR the name and company and resolve the person with POST /person_detail_lookup/.
What inputs does it take and what does it return?
⌄
You send company domain, full name + company domain and LinkedIn URL or public identifier. You get back phone_number, work_email, company and person, from POST /person_contacts_lookup/phone_numbers/, as JSON.
Can our users see Forager data in our product?
⌄
Yes, under platform terms. Self-serve plans cover internal use by your own team. Showing Forager contacts to your users, or passing records on, is licensed separately: talk to sales about volume and which fields your users need to see.
Am I charged when no mobile number is found?
⌄
No. A mobile number lookup that finds nothing costs 0 credits, so you pay for mobile numbers we find. Search, enrichment and reverse lookups are the exception: they are charged per request.
Can AI agent builders test mobile numbers for free?
⌄
Yes. Create a free account at app.forager.ai: it comes with $5 in free credits and an API key, and there is no credit card to sign up. Run it on records you already know, or book a demo and send us a list: we run it and show you what we find.
How do I add a contact waterfall to my agent's tools?
⌄
Define one find_contact tool in your framework that takes a LinkedIn URL or name and company. Inside it, call POST /person_contacts_lookup/phone_numbers/ then POST /person_contacts_lookup/work_emails/ when the earlier source returns nothing.
How do you check data quality?
⌄
Forager ranked #1 of 10 in Clay's 2026 test of mobile data providers, by quality score: Clay's measure of how likely a dialled number reaches the right person. The test that counts is your own: send a list of profiles you care about. We run it and show you what we find, number by number, so you can measure hit rate and connect rate yourself.
How is a mobile number lookup API different from a contact database?
⌄
A contact database sells access to a list, often by seat or by export. A lookup API answers one person at a time inside your product or workflow: you send the LinkedIn URL or email you already hold and get back a mobile number in one JSON response. With Forager a mobile number lookup that finds nothing costs 0 credits, so you pay for numbers, not for searches.
Where can I use Forager mobile numbers?
⌄
Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Everything else connects through the REST API with one API key.
Written answers are not available right now. The matching pages above still help, or book a demo and ask the team.
