Launch a pay-per-valid-result phone finder on wholesale mobile data

Let a contact-data vendor sell a phone-finder subscription or credit pack, charging its users only for valid numbers while paying a wholesale supplier per found result.

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 teams on Forager

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

What it costs: 15 credits per mobile found. A mobile or email lookup that returns nothing costs 0 credits. Enrichment and search are charged per request: credit pricing.

How the data flows

3 inputs → Mobile numbers + Person enrichment → 4 fields sample data

01 · Inputs

LinkedIn URL

linkedin.com/in/alex-sample

Company domain

example.com

person_id

per_8f3a1c

02 · Forager

Mobile numbers + Person enrichment POST /person_detail_lookup/

Match found

03 · Outputs

Alex SampleVP Revenue Operations · Example Inc.

phone number: +1 (212) 555-0199
phone type: mobile
valid: true
name: Alex Sample
title: VP Revenue Operations
work email: alex@example.com

3 fields in the responseexample data

Steps

Resolve the person from a profile URL or name + company with POST /person_detail_lookup/
Call POST /person_contacts_lookup/phone_numbers/ with Gold for premium plans and Silver (a nested superset of Gold) for volume plans
Run the vendor's own validity check and charge the end user only on a valid result
Track margin per plan from found-only supplier billing

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 person from a profile URL or name + company with POST
# /person_detail_lookup/
r1 = requests.post(f"{BASE}/person_detail_lookup/", headers=HEADERS, json=body)

# 2. Call POST /person_contacts_lookup/phone_numbers/ with Gold for premium
# plans and Silver (a nested superset of Gold) for volume plans
r2 = requests.post(f"{BASE}/person_contacts_lookup/phone_numbers/", headers=HEADERS, json=body)

# 3. Run the vendor's own validity check and charge the end user only on a
# valid result

# 4. Track margin per plan from found-only supplier billing

# 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

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
profile URL	`phone_number`
name + company domain	`phone_type`
person_id	`tier`
	`valid (bool)`

Questions about this recipe

Where can a data vendor source mobile numbers wholesale for its own phone finder?

This recipe uses Forager Mobile numbers and Person enrichment. Mobile numbers: Direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Let a contact-data vendor sell a phone-finder subscription or credit pack, charging its users only for valid numbers while paying a wholesale supplier per found result.

What does it cost to launch a pay-per-valid-result phone finder on wholesale mobile data?

Mobile numbers: 15 credits per mobile number found, and a mobile number lookup that finds nothing costs 0 credits. Person enrichment: 1 credit per request, charged whether or not data comes back. Growth's 8,250 monthly credits cover 550 mobiles or 8,250 person enrichments, 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 name + company domain, person_id and profile URL. You get back phone_number, phone_type, tier and valid (bool), as JSON. You also need a Forager API key, which comes with a free account.

Which mobile number API bills only on found results?

Can I 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.

When should I run this workflow?

When a vendor known for email finding adds a phone product, or reprices a phone finder to compete on cost. The vendor's users get mobiles at a predictable price per valid number, and the vendor keeps margin on every plan.

Which Forager products does this recipe use?

Mobile numbers and person enrichment. Mobile numbers: direct mobile numbers for a person, from a LinkedIn URL or a Forager person ID, validated before they reach you. Person enrichment: a full professional profile for a person from a LinkedIn URL, email or phone: experience, education, skills and contact channels.

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?

4 steps: resolve the person from a profile URL or name + company with POST /person_detail_lookup/, call POST /person_contacts_lookup/phone_numbers/ with Gold for premium plans and Silver (a nested superset of Gold) for volume plans, run the vendor's own validity check and charge the end user only on a valid result and track margin per plan from found-only supplier billing.

Do I need a subscription?

Not to test: 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 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.

A selection of teams that run this job on Forager · plus other teams on Forager

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.
Andela
- Customer
Selected use case: Forager data for the go-to-market team at a global talent marketplace.
Coram
- Internal use
Selected use case: mobile numbers for outbound calling.
HubSpot
- CRM add-ons
Selected use case: enriching contact and company records with people, company and job-posting data.
Airscale
- Waterfall enrichment
Selected use case: a Forager step in its mobile number waterfall.
SeekOut
- Talent intelligence
Selected use case: Forager’s people data feed, used to keep candidate profiles current.

2–3 years on the Forager people data feed, by SeekOut’s own account¹

Sources

¹ SeekOut: SeekOut, customer interview, Sep 2026.

Launch a pay-per-valid-result phone finder on wholesale mobile data

How the data flows

Steps

Inputs and outputs

Questions about this recipe

Where can a data vendor source mobile numbers wholesale for its own phone finder?

What does it cost to launch a pay-per-valid-result phone finder on wholesale mobile data?

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

Which mobile number API bills only on found results?

Can I test mobile numbers for free?

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?

Do I need a subscription?

Can our users see Forager data in our product?

More recipes for contact-data vendors

Back a sales-intelligence database with an additional mobile source

Launch a regional B2B contact database on licensed people and jobs feeds

Bundle job-posting buying signals into a B2B data product

Resell person and reverse-email enrichment through a developer data API

Add an additional email source to an email finder's lookup chain

Fill missing emails and mobiles in user-uploaded CSVs

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