People Data API Pricing: How Caching Cuts Lookup Costs

People data API pricing is difficult to compare because vendors charge for different units: a request, a match, a contact field, a credit, or an exported record. Before comparing headline prices, define what one paid unit actually returns.

Personpages uses one pay-as-you-go plan. Every API key gets 50 free lookups per calendar month across person and website endpoints. After the free allowance, a newly researched result costs $0.39 and a result already saved in the Personpages cache costs $0.05.

New lookup versus cached lookup

A new lookup requires fresh research and profile generation. A cached lookup returns a saved result without repeating that work, so it is faster and costs less.

The API response includes a cached boolean. Use it in usage reporting, cost analysis, and quality monitoring instead of trying to infer result type from response time.

Simple cost examples

If an application makes 1,000 lookups in a month and 300 are cached, the first 50 total lookups are free. The exact bill depends on which requests fall inside that allowance. A conservative forecast treats the remaining 950 as new: 950 × $0.39 = $370.50. If 300 of those billable requests are cached, the estimate becomes 650 × $0.39 + 300 × $0.05 = $268.50.

For 10,000 billable lookups with a 40% cache rate, the estimate is 6,000 × $0.39 + 4,000 × $0.05 = $2,540. Your real cache rate depends on how often users research the same people or domains.

How to forecast your own bill

1. Estimate monthly completed profile and website lookups, not free candidate searches.
2. Subtract the 50-lookups monthly allowance.
3. Estimate the percentage likely to be cached.
4. Multiply new lookups by $0.39 and cached lookups by $0.05.
5. Run a small real workload and replace assumptions with the cached field from responses.

Billing behavior to design for

A payment card is saved when an API key is created. Usage after the free allowance accrues during the day and is charged daily. Very small balances below the payment processor's $0.50 minimum roll forward rather than producing tiny charges.

If a charge fails, the key is blocked and requests return a payment error until the card works again. Production integrations should alert on HTTP 402 and stop automated retries; repeated requests cannot fix a declined card.

Ways to control data costs

• Resolve candidates before requesting a full profile; candidate discovery is free.
• Avoid accidental duplicate calls caused by client re-renders or job retries.
• Store the profile URL and result you received when your use case permits it.
• Track endpoint, cached status, and billed amount from your developer dashboard.
• Use an idempotent job queue so a timeout does not create parallel requests.
• Set internal daily alerts even though the API itself has no spending cap.

Compare APIs on usable results

The cheapest request is not the cheapest correct record. Include false-match review, stale data, missing source evidence, and integration time when comparing providers. A candidate-first API can cost more per generated profile while costing less per profile your team can actually trust.

Start with real traffic

Create an API key to test 50 lookups free each month, then use the API documentation to integrate people and website reports.