Most articles answering this query will tell you the product no longer exists. That was true for a while and it is not true now. As of 4 September 2026 there is a live Whitepages Pro API with a public pricing page, a self-serve plan, a free trial and a published rule for what counts as a billable query. This guide reads that rate card the way a buyer should — starting with the definitions, not the dollar figure.
Disclosure: Scout Data is our product; treat that entry as a maker’s pitch and the rest as our honest read.
Three products have carried this name
Before pricing anything, establish which one you are pricing. They have different owners, different licensing and — critically — different answers to “what does it cost”.
| What you might mean | What it is | Published price |
|---|---|---|
| Whitepages Pro API (today) | People and property data API sold by Whitepages; contact enrich, refresh and verify | Yes — per query, on a public page |
| Whitepages Pro (2019 and earlier) | The B2B arm that spun out as Ekata and was acquired by Mastercard in 2021 | No — enterprise quote, contact sales |
| Whitepages consumer lookups | The consumer-facing people search at whitepages.com, sold as a subscription | Disclosed inside its own signup flow; a consumer product with consumer licensing |
Only the first row has a rate card, so the rest of this page is about the first row. If you were shopping the second, the successor sells identity verification and fraud decisioning to payments companies and is priced by contract; if you were shopping the third, read the terms of use for that specific product before you put results into a business workflow, because a consumer subscription is licensed for consumer use.
The published rate card
As publicly advertised on 4 September 2026 on the Whitepages Pro API pricing page:
| Plan | Published rate | Volume |
|---|---|---|
| Trial | Free | 50 queries over 14 days, no card required |
| Essentials | $0.22 per query — $220/mo | 1,000 queries, overage billed at $0.22 |
| Higher Volume | As low as $0.15 per query | 2,500–30,000 queries per month |
| Above 50,000 queries per month | Custom quote | Contact sales |
Pricing on this page is as publicly advertised at the time of writing — confirm current pricing with each vendor, and with our sales team for Scout Data.
The commercial terms around those numbers are unusually clearly stated, and they are worth quoting because most vendors leave them to the contract: billing is monthly on autopay, overages land on the following month’s invoice, you can upgrade or downgrade at the start of the next cycle, and usage is measured in Pacific Time. Whitepages describes the underlying graph as built on 28 years of US identity resolution, with 350 million identity records, 673 million phone and address records, 571 million email addresses and 112 million property records.
The two rules that decide your bill
Per-query pricing is only as meaningful as the definition of a query, and this rate card publishes two rules that matter more than the rate itself.
A billable query is defined by HTTP status. Any Person or Property request returning a 2xx success or a 4xx client error bills; 429 rate limits and 5xx server errors do not. That is admirably unambiguous from an engineering standpoint, and it is worth understanding what it implies commercially: your own malformed request bills, and a request that succeeds technically bills on its status code rather than on the richness of what came back. Before you build a model, ask their team directly what a clean no-match returns and whether it bills. Get the answer in writing and put it in the spreadsheet.
Unused queries do not roll over. Allocations reset each billing cycle. If your outbound volume is seasonal — and in roofing and solar it always is — you either size the plan for your peak and pay for the peak twelve times, or size it for your average and pay overages in the months that matter most. Neither is wrong; both are decisions you should make deliberately rather than discover in March.
What $0.22 becomes across a real file
Multiply the published rate by volumes an outbound team actually runs. These are arithmetic on the advertised numbers, not quotes.
- 5,000 records a month at $0.22 is $1,100 — comfortable, and roughly the scale the self-serve tier is shaped for.
- 25,000 records a month at $0.22 is $5,500. At the advertised higher-volume floor of $0.15 the same file is $3,750, though 25,000 is near the top of the published band.
- 100,000 records a month is past the published card entirely and into a custom quote, which is where the comparison stops being a rate-card comparison at all.
That progression is the honest summary of per-query pricing everywhere, not a criticism of this vendor: it is excellent at the volume where you are enriching records one at a time as they arrive, and it converts into a different kind of conversation the moment your unit of work becomes a weekly file. The same shape, at different rates, shows up in Searchbug alternatives and inverts at the cheap append end in DataZapp alternatives.
Turning a query rate into a number you can compare
A per-query price is not comparable to a per-record price until you put both over the same denominator. The one that predicts your cost per booked appointment is cost per dialable contact: total spend for the run divided by records that produced a working number reaching the person you meant to reach. Two vendors ten cents apart on the sticker routinely swap places on that number, and the worksheet for computing it is in our skip tracing cost calculator.
Use the free trial for exactly this. Fifty queries is not enough to measure a match rate, but it is enough to check whether the returns are shaped like what you need — whether the phone comes back attached to the name you sent or merely to the address, which is the distinction that decides everything downstream. For the wider field of vendors priced per record rather than per query, start with best skip tracing software.
Four questions before the first invoice
- What does a clean no-match return, and does it bill? The published rule answers this by status code; get the practical answer in writing.
- Which endpoint am I actually going to call? Person and Property are different requests with different useful outputs. Model the one you will run in production, not the cheapest one.
- What is my peak month? With no rollover, the peak is the plan-sizing input, not the average.
- What happens above 50,000? If you expect to cross it within a year, have the custom-quote conversation before you build the integration, not after.
Frequently asked questions
Is this the same Whitepages Pro that became Ekata?
No, and this is the trap in the query. The business-to-business arm that spun out in 2019 and rebranded as Ekata was acquired by Mastercard in 2021 in a deal reported at $850 million; as of 4 September 2026, ekata.com redirects to a Mastercard identity page. The Whitepages Pro API you can buy today is a separate, current product sold by Whitepages itself, with published per-query pricing. Same words, different purchase. The fuller history is in Whitepages Pro alternatives.
Do I get charged for a query that finds nothing?
Read the published rule carefully. Whitepages states that a billable query is any Person or Property request returning a 2xx success or a 4xx client error, and that rate-limit (429) and server-error (5xx) responses are not billable. That is a rule about HTTP status, not about whether the answer was useful — a successful call that comes back thin still succeeded. Confirm the specific no-match behaviour with their team before you model it either way.
Do unused queries carry over to next month?
No. The pricing FAQ states that unused queries do not roll over and each month’s allocation resets at the start of the billing cycle. That single sentence is worth more than the per-query rate when you size a plan, because it means a lumpy month-to-month volume gets billed at its peak rather than its average.