People Data API Pricing: Per-Call, Credit and Seat Models

People data API pricing comes in three shapes: a fee per call, a pool of credits, or a per-seat subscription. BusinessMCP charges per call, at $0.08 per search item, $0.04 for an email finder lookup and $0.10 for enrichment, only when a result is found, on a prepaid balance from $10 with no subscription.

The three billing models

Before comparing numbers, compare units. A price of “$0.04” and a price of “one credit” are not comparable until you know what a credit costs and what it buys.

Model	How you pay	Good for	Watch out for
Per call	A set fee per request or per returned item	Low, spiky or agent-driven volume	Costs scale linearly with no volume discount unless stated
Credits	A pool bought up front, spent at different rates per action	Mixed usage with a predictable monthly volume	Different actions burn different amounts of credits; unused credits may expire
Seats	A monthly fee per user, with an allowance	A team of reps who work in a vendor’s own app	Paying for seats that API integrations barely use

Per-call billing is simplest to reason about, which is why it suits developers and AI agents that call an API a few times a day and then stop. Seat models suit teams that live inside a vendor’s interface, where the API is an add-on.

What BusinessMCP publishes

The People Data API page lists these prices.

Endpoint	Price	Unit
People search	$0.08	Per item returned
Email finder	$0.04	Per call
Person enrichment	$0.10	Per call

All three are charged only when a result is found. Billing is prepaid from $10, with no subscription. The page says the free trial never pays for people calls, and that people endpoints require a purchased balance and acceptance of terms that include a declared intended use. The free credit amount is not stated on that page, and BusinessMCP’s company-data pages mention $5 of free credit for 7 days for the company, IP and similar tools, so treat the trial as applying to those, not to people data.

The page states no rate limits and no volume discount tiers. BusinessMCP’s own comparison page concedes that its per-record price “is not the lowest at volume”, which is a useful admission to weigh against its simplicity.

Key takeaway: the cheapest sticker price is not the cheapest outcome. Compute cost per usable contact, which includes misses, bounces and wrong matches.

Comparing against other pricing models

BusinessMCP’s comparison of company and people data APIs gathers figures for other providers with citations, and says they were checked in late September and early October 2026. It reports, for example, that ZoomInfo’s per-credit access is about $0.38 each at the $1,000 spend tier, that Apollo bills an email at one credit and a phone number at eight with seats from $49 to $119 per user per month on annual billing, and that Hunter charges one credit for a found email and half a credit for a verification. These are the comparison page’s figures; verify them on each vendor’s site before you decide, since vendor pricing changes often.

Note what is not in that list. Phone numbers are priced at a premium by credit vendors, and BusinessMCP does not offer phone data at all. If calling is central to your motion, per-call pricing on email-only endpoints is not a like-for-like substitute.

Calculating cost per usable contact

Use a small experiment and a simple formula.

1. Choose a sample of 200 target people or accounts.
2. Run them through each candidate provider.
3. Count results found, then results that pass your own checks: right person, current employer, address not bounced.
4. Divide total spend by the number of usable results.

A worked example, with invented round numbers for illustration only. Provider A charges $0.04 per found email and finds 120 of 200 names, of which 100 deliver. Spend: 120 × $0.04 = $4.80, so $0.048 per delivered address. Provider B charges $0.03 per attempt, finds 150, and 105 deliver. Spend: 200 × $0.03 = $6.00, so about $0.057 per delivered address. B has the lower sticker price and the higher outcome price. This is why the unit of billing matters as much as the number.

Hidden costs to price in

• Compliance overhead. Handling opt-outs, logging purposes and legal review costs time. BusinessMCP logs every people call with the declared purpose, and you should mirror that internally. See people data and GDPR.
• Coverage gaps. If the provider excludes your main market, the cheapest price buys nothing. BusinessMCP excludes the EU, EEA, UK and Switzerland, and several US states.
• Re-verification. Contact data decays as people change jobs. Budget for refreshes, not just first pulls.
• Engineering time. Credit systems need balance tracking and retry logic. Per-call systems need spend alerts instead.
• Minimum top-ups. A $10 minimum is small, but verify whether the balance expires.

Controlling spend in practice

Cap the damage with a few controls: set a maximum limit on search calls in your code, deduplicate inputs by lowercase email or domain before you call, cache results with a timestamp, and alert when daily spend crosses a threshold. For agent-driven workflows, put a hard budget in the agent’s instructions. Our piece on using people data from AI agents covers that setup. If your question is purely account-level, the cheaper company data endpoints at $0.01 to $0.02 per found item may answer it without touching people data at all.

Deciding

If your volume is small, irregular or agent-driven, per-call is easy to justify. If you run thousands of enrichments every week and your team works inside a vendor’s app, a seat or credit plan may be cheaper, and it may bring phone data and intent signals that a lean API lacks. Whichever route you pick, run the sample test first, and read how to choose the best provider before signing anything.