Every product draws on the same records and one credit balance.
GDPR compliance“They've earned our trust when connect rates matter most.”
Aaron Joseph, Head of BizOps, Orbital
Customer storiesGet $5 in free credits, then your API key and your own sample from the docs.
Get $5 free
API, data feeds and the app
By platform, segment and industry
API docs, integrations, guides
Reach the right person.
What CRM add-ons need from mobile numbers, what Forager returns, and how teams like yours test it.
1 recipe uses mobile numbers for CRM add-ons, copilots, browser-to-CRM tools.
A selection of CRM add-ons using Forager for mobile numbers · plus other sales-tech platforms
When to use it: A rep clicks 'enrich' on a CRM contact or a profile page.
linkedin_public_identifier or email to the platform's waterfallPOST /person_detail_lookup//work_emails/ and POST /person_contacts_lookup/phone_numbers/| Inputs | Outputs |
|---|---|
| LinkedIn URL | work_email |
| CRM contact id | phone_number |
role_title |
When to use it: A waterfall platform reviews per-provider hit rates and wants more found mobiles per list without raising cost per number.
Show the stepslinkedin_public_identifier (or person_id from person_detail_lookup) to POST /person_contacts_lookup/phone_numbers/phone_number to E.164 and map it to the platform's phone field with provider attribution| Inputs | Outputs |
|---|---|
| LinkedIn URL or public identifier | phone_number |
| person_id | phone_type |
| full name + company domain (resolved upstream) | tier |
provider | |
found (bool) |
work_emailphone_numberrole_titlephone_typetierproviderfound (bool)From the workflows above. Full field reference: Mobile numbers and the Mobile numbers API reference.
Your users place the call, so the number has to connect. Gold is our highest-confidence set.
How the tiers workA selection of CRM add-ons using Forager for mobile numbers · plus other sales-tech platformsA selection of teams using Forager
Nooks Selected use case: mobile numbers inside their dialer.
Amplemarket Selected use case: mobile numbers inside its contact waterfall.
Clay Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
Airscale Selected use case: a Forager step in its mobile number waterfall.
Monaco Selected use case: mobile data in its enrichment waterfall.
Orbital Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.
BetterContact Selected use case: a Forager step in its waterfall for mobile numbers.
HubSpot 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.”
Fill contact records with email and mobile inside the CRM or browser extension reps already use. Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. This page walks through 3 workflows with the exact steps.
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
Fill CRM records with contacts that connect. Products like yours are judged on connect rate and cost per valid result, 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.
Extension sends linkedin_public_identifier or email to the platform's waterfall. Return work email and mobile from /work_emails/ and POST /person_contacts_lookup/phone_numbers/.
You send LinkedIn URL, LinkedIn identifier and LinkedIn identifiers. You get back phone_number, role_title, work_email and organization, from POST /person_contacts_lookup/phone_numbers/, as JSON.
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.
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.
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.
The workflow uses Forager Mobile numbers, Work emails, Person enrichment and People search. Mobile numbers: Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Give a global outbound team usable mobiles and work emails for EMEA and French/EU decision makers where US-centric sources run thin.
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.
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.
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.
Give GTM engineers a mobile, email and person provider they can drop into any table, workflow or waterfall step, billed in platform credits.
See the recipeLet an AI SDR turn a natural-language prompt into a running sequence with verified emails and phones for every prospect.
See the recipeTurn thousands of stale CRM accounts into callable contacts by refreshing people, roles and channels in one pass.
See the recipeReturn the full buying committee (economic buyer, champion, technical evaluator) for an account so reps and agents can multi-thread deals.
See the recipeLet a sequencing platform add call steps by finding mobiles for the leads already in a campaign.
See the recipeFill the number waterfall behind a power or parallel dialer so SDRs spend sessions talking to buyers, not hunting numbers.
See the recipeSend us a list. We run it, show you what we find, then talk volume and terms.
