“Whitepages” is three products with three price tags, and which one you mean decides whether the answer is a monthly consumer subscription, an API billed per query, or a sales call. Most articles answering this query will also tell you that Whitepages Pro 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 puts the three prices side by side first, then reads the Pro API 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.
The short answer: three products, three prices
| What you might mean | What it is | Published price |
|---|---|---|
| Whitepages, and Whitepages Premium | The consumer people-search site at whitepages.com; Premium is its paid subscription, licensed for personal use | $22.95 per month, as publicly advertised October 2026 |
| Whitepages Pro API (today) | People and property data API sold by Whitepages to businesses; contact enrich, refresh and verify | $0.35 per query in one-time packs, $0.15–$0.22 on monthly plans, as low as $0.08 on custom contracts (October 2026); free trial of 50 queries |
| Whitepages Pro (2019 and earlier), now Ekata | The B2B arm that spun out as Ekata and was acquired by Mastercard in 2021; identity verification for payments companies | No public rate card — enterprise 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.
If you want to look one person or one address up for yourself, the first row is your product and Whitepages Premium cost is the page to read. If you are pricing an integration that enriches records as they arrive, the second row is yours and the rest of this page is about it. If you were shopping the third, the successor sells fraud decisioning to payments companies and is priced by contract; the alternatives for what it used to do are in Whitepages Pro alternatives.
1. Whitepages and Whitepages Premium: the consumer subscription
The consumer site is what most people picture when they type the brand name. Its paid tier is Whitepages Premium — searched as one word nearly as often as two — publicly advertised at $22.95 per month as of October 2026, for people searches, reverse phone lookups and address lookups on a personal basis. There is no per-lookup fee on that subscription, and there is no rate card either, because it is not sold by volume.
That is also why it does not belong in a business pricing comparison. The terms of use license it for personal purposes; there is no bulk export, no owner-of-record match against the deed, and no do-not-call scrub, so the moment the job becomes a list rather than a lookup the product stops fitting regardless of price. What the subscription does and does not include, and when it is genuinely the right answer, is covered separately in Whitepages Premium cost.
2. Whitepages Pro, Ekata and Mastercard: the one that went away
The Whitepages Pro that many teams remember — the B2B lookup API and its review tool — spun out of the consumer company in 2019 and rebranded as Ekata. Mastercard acquired Ekata in 2021 in a deal reported at $850 million, and as of 4 September 2026 ekata.com redirects to a Mastercard identity page. The product that survives sells identity verification and fraud decisioning to payments companies, and it is priced by contract: there is no public rate card and no self-serve signup.
If that is what you were looking for, the question is no longer what it costs but what to use instead for the job it used to do — reverse lookups, phone append, list building — and that comparison lives in Whitepages Pro alternatives. The rest of this page is about the product that carries the name today.
3. The Whitepages Pro API: the published rate card
As publicly advertised on 4 October 2026 on the Whitepages Pro API pricing page, which has been restructured since the September version of this guide:
| Plan | Published rate | Volume |
|---|---|---|
| Trial | Free | 50 queries over 14 days, no card required |
| One-Time | $0.35 per query | Packs of 100 to 2,500 queries, used within 90 days, no overage |
| Always On | $0.15 to $0.22 per query | 1,000–30,000 queries per month, overage billed at the plan rate |
| Custom | As low as $0.08 per query | Up to 250,000 queries per month, through sales |
The commercial terms around those numbers are unusually clearly stated, and they are worth quoting because most vendors leave them to the contract. The October 2026 pricing FAQ says queries beyond a monthly plan are billed at that plan’s per-query rate, and that unused queries do not roll over. The September 2026 version of the page added that billing is monthly on autopay and usage is measured in Pacific Time, and described 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.
4. 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. As the September 2026 rate card put it, 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.
5. What $0.15–$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.15 to $0.22 is $750 to $1,100 — comfortable, and roughly the scale the self-serve tier is shaped for. Bought as one-time packs at $0.35 it would be $1,750.
- 25,000 records a month at $0.15 to $0.22 is $3,750 to $5,500, near the top of the 30,000-query Always On band.
- 100,000 records a month is past the self-serve card and into a custom contract advertised from $0.08 a query, so from $8,000 a month — 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.
6. Is there a Whitepages free trial?
For the Pro API, yes, and it is on the rate card: 50 queries over 14 days with no card required. For Whitepages Premium, the consumer site runs its own promotions and they change — check the current offer on their site rather than trusting a figure from a third-party article, this one included. For Ekata there is nothing to trial; it is sold by contract, so the way in is a sales conversation.
Use the API trial for one specific purpose. 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. Send it records you already know the answer for, so the 50 tell you something.
7. 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.
For the wider field of vendors priced per record rather than per query, start with best skip tracing software.
8. Alternatives to Whitepages for property lookup
A large share of the people searching this brand are not pricing an API at all; they want to know who owns or lives at an address, and Whitepages is simply the name they remember. The right alternative depends on which of three questions you are asking.
| If you need to… | Use |
|---|---|
| Find who owns one house | The county assessor’s search — free and authoritative. The steps are in how to find out who owns a house |
| Resolve a list of addresses to owners and occupants | Bulk property records rather than a lookup site — see reverse address lookup for sales teams |
| Reach the owner by phone | A skip-tracing or phone-append vendor — see finding a homeowner’s phone number |
| Replace the old Whitepages Pro at work | The vendor-by-vendor comparison in Whitepages Pro alternatives |
9. 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, review Whitepages API pricing and have the custom-quote conversation before you build the integration, not after.
Frequently asked questions
How much does Whitepages Premium cost?
Whitepages Premium is the paid subscription on the consumer site, publicly advertised at $22.95 per month as of October 2026, and licensed for personal people-search and reverse-lookup use. It is not the same product as the Whitepages Pro API, which is sold to businesses per query at $0.15 to $0.35 depending on the plan, as advertised in October 2026. What the subscription includes, and why it is the wrong tool for a calling list, is covered in Whitepages Premium cost.
Does Whitepages have a free trial?
The Whitepages Pro API does: 50 queries over 14 days with no card required, as published on its pricing page. The consumer subscription, Whitepages Premium, runs its own promotions and they change — check the current offer on their site rather than relying on a figure from a third-party article. The former Whitepages Pro, now Ekata inside Mastercard, is sold by contract, so the way in is a sales conversation rather than a trial button.
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.