Give an AI SDR a verified mobile before it dials

Let an AI SDR or voice agent look up a mobile number and work email for the person it is about to contact, as one typed tool call, so it dials and writes to the right person.

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

A selection of teams that run this job on Forager · plus other sales-tech platforms

Tools named: LinkedIn

Uses POST /person_detail_lookup/, POST /person_contacts_lookup/phone_numbers/, POST /person_contacts_lookup/work_emails/ · Person enrichment API reference

What it costs: 15 credits per mobile found · 5 credits per email found. A mobile or email lookup that returns nothing costs 0 credits.

Mobile numbers
Work emails
API
Embedded in a platform
Sales tech

How the data flows

3 inputs → Mobile numbers + Work emails → 5 fields sample data

01 · Inputs

LinkedIn URL

linkedin.com/in/jane-example

Company domain

example.com

person_id

per_8f3a1c

02 · Forager

Mobile numbers + Work emails POST /person_detail_lookup/

Match found Pay per field · Empty result: 0 credits

03 · Outputs

Jane ExampleVP Revenue Operations · Example Inc.

phone number: +1 (415) 555-0142
phone type: mobile
work email: jane@example.com
person id: per_8f3a1c
found: true
name: Jane Example

5 fields in the responseexample data

Steps

Resolve the prospect to a Forager person_id with POST /person_detail_lookup/ (LinkedIn URL or name and company domain)
Call POST /person_contacts_lookup/phone_numbers/ and POST /person_contacts_lookup/work_emails/ from the agent's contact tool
Hand the agent the number and email as structured fields, never as free text it has to parse
Log the person_id against the call so a wrong number can be reported and the record re-checked
Retry nothing: an empty result costs 0 credits and the agent moves to the next prospect

import json, os, requests

BASE = "https://api-v2.forager.ai/api/{account_id}/datastorage"
HEADERS = {"X-API-KEY": os.environ["FORAGER_KEY"]}
body = json.load(open("request.json"))  # request fields: see the API reference

# 1. Resolve the prospect to a Forager person_id with POST
# /person_detail_lookup/ (LinkedIn URL or name and company domain)
r1 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body)

# 2. Call POST /person_contacts_lookup/phone_numbers/ and POST
# /person_contacts_lookup/work_emails/ from the agent's contact tool
r2 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)
r3 = requests.post(f"{BASE}/person_contacts_lookup/work_emails/", headers=HEADERS, json=body)

# 3. Hand the agent the number and email as structured fields, never as free
# text it has to parse

# 4. Log the person_id against the call so a wrong number can be reported
# and the record re-checked

# 5. Retry nothing: an empty result costs 0 credits and the agent moves to
# the next prospect

# 1. POST /person_detail_lookup/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_detail_lookup/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

# 2. POST /person_contacts_lookup/phone_numbers/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/phone_numbers/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

# 3. POST /person_contacts_lookup/work_emails/
curl -X POST \
  https://api-v2.forager.ai/api/{account_id}/datastorage/person_contacts_lookup/work_emails/ \
  -H "X-API-KEY: $FORAGER_KEY" \
  -H "Content-Type: application/json" \
  -d @request.json

Generated from the recipe stepsRequest fields: API reference

Run it yourself: Person enrichment API reference

Get a free API key + $5 Get a sample run

Free API key
No credit card
Run your sample

Inputs and outputs

Inputs	Outputs
LinkedIn URL or public identifier	`phone_number`
full name + company domain	`phone_type`
person_id	`work_email`
	`person_id`
	`found (bool)`

Questions about this recipe

How can my AI SDR get a verified mobile number before it calls a prospect?

Resolve the prospect to a Forager person_id with POST /person_detail_lookup/ (LinkedIn URL or name and company domain). Call POST /person_contacts_lookup/phone_numbers/ and POST /person_contacts_lookup/work_emails/ from the agent's contact tool.

What does it cost to give an AI SDR a verified mobile before it dials?

Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Work emails: 5 credits per work email found, and a work email lookup that finds nothing costs 0 credits. Growth's 8,250 monthly credits cover 550 mobiles or 1,650 emails, or a mix. Self-serve plans are Starter, Growth, Pro and Scale. See plans and prices

What do I need to run this recipe, and what comes back?

You send full name + company domain, LinkedIn URL or public identifier and person_id. You get back found (bool), person_id, phone_number and phone_type, as JSON. You also need a Forager API key, which comes with a free account.

Which contact data API works as a tool for a sales agent?

This recipe uses Forager Mobile numbers and Work emails. Mobile numbers: Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Let an AI SDR or voice agent look up a mobile number and work email for the person it is about to contact, as one typed tool call, so it dials and writes to the right person.

Is there a free way to try Forager on this workflow?

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.

When should I run this workflow?

An AI SDR picks a prospect from its queue and has a LinkedIn URL or a name and company, but no number to dial. The AI SDR reaches the person it meant to call, and the platform pays only for the numbers and emails it actually found.

Which Forager products does this recipe use?

Mobile numbers and work emails. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Work emails: verified work email addresses for a person at their current employer.

How do I know the data is right?

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.

Which tools can run this workflow?

Native in Clay and Zapier, partner-built in Deepline and Cargo and called through the API from Make, n8n and your own code. Or call the endpoints in the steps above from your own code with one API key.

How many steps is this workflow?

5 steps: resolve the prospect to a Forager person_id with POST /person_detail_lookup/ (LinkedIn URL or name and company domain), call POST /person_contacts_lookup/phone_numbers/ and POST /person_contacts_lookup/work_emails/ from the agent's contact tool, hand the agent the number and email as structured fields, never as free text it has to parse, log the person_id against the call so a wrong number can be reported and the record re-checked and retry nothing: an empty result costs 0 credits and the agent moves to the next prospect.

Is there a contract or minimum commitment?

No contract to start: a free account comes with $5 in credits. To keep using Forager, choose a monthly or yearly plan. Monthly plans cancel anytime and unused credits roll over; yearly plans grant all credits upfront and cost 10% less. Larger volumes are agreed with our team.

Can we show Forager data inside 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.

A selection of teams that run this job on Forager · plus other sales-tech platforms

Clay
- GTM workflow builders
Selected use case: Forager mobile numbers, emails and people data inside Clay tables.
Juicebox
- AI candidate sourcing
Selected use case: Forager data behind its PeopleGPT search and sourcing agents.
Nooks
- Power & parallel dialers
Selected use case: mobile numbers inside their dialer.
Amplemarket
- AI SDRs
Selected use case: mobile numbers inside its contact waterfall.
Roger
- AI SDRs
AI outbound sales rep.
HubSpot
- CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
Jeeva AI
- AI SDRs
Agentic platform of AI digital workers for sales teams.
Orbital
- Lead databases
Selected use case: contact lookups in its enrichment waterfall, for teams selling to local businesses.

Give an AI SDR a verified mobile before it dials

How the data flows

Steps

Inputs and outputs

Questions about this recipe

How can my AI SDR get a verified mobile number before it calls a prospect?

What does it cost to give an AI SDR a verified mobile before it dials?

What do I need to run this recipe, and what comes back?

Which contact data API works as a tool for a sales agent?

Is there a free way to try Forager on this workflow?

When should I run this workflow?

Which Forager products does this recipe use?

How do I know the data is right?

Which tools can run this workflow?

How many steps is this workflow?

Is there a contract or minimum commitment?

Can we show Forager data inside our product?

More recipes for AI SDRs

Power an AI SDR's email and phone waterfall from a chat prompt

Source a role-tagged buying committee for every target account

Qualify PLG sign-ups and route enterprise accounts to sales

Enrich leads before an AI agent writes personalized campaign copy

Build an AI SDR's daily call list from hiring signals

Extend phone and email coverage for European outbound

Put people, company and job data your users can act on inside your product