Loqate vs RevAddress: What Address Verification Costs in 2026

Loqate, a GBG company and formerly PCA Predict, publishes its pay-as-you-go rates. That is worth saying up front, because the widely repeated claim that Loqate hides all pricing behind sales is out of date and this page used to repeat it.

What Loqate does not publish is the price of the product you are probably comparing. Capture, the type-ahead that pulls an address out of a user’s first few keystrokes, has a rate on the page. Verify, the one that takes a record you already hold and checks it against postal records, reads POA. Price on application.

That gap is the story. Here is the published side, what it works out to at volume, and what a flat USPS-native plan costs instead. Every Loqate figure below was read from Loqate’s own pages on August 23, 2026.

What Loqate publishes

Pay-as-you-go, priced by the size of the credit pack you buy. The larger the pack, the lower the unit rate.

Three conditions ride with those numbers. Credit is valid for 12 months from purchase. Prices exclude VAT. The free trial runs 45 days with no credit card, which is generous, and it is a trial rather than an ongoing free tier.

There is one question to settle before you model anything off the Capture rate: ask Loqate how your traffic counts. Capture is a type-ahead surface, and a single finished address can involve more than one call as the user types. The rate is per lookup, not per address captured, and the ratio between the two is a property of your integration rather than of the price list.

What the published rate costs at volume

Take 4.1c, the best published US rate, which requires buying in $1,000 packs. One such pack is about 24,400 lookups, so a team validating 25,000 US addresses a month is buying roughly one pack a month.

At 1,000 a month you would be buying the $100 pack, so the real entry rate is 4.7c and the monthly figure is nearer $47.

On annual billing at 10,000 a month, that is about $4,920 a year against $758. The shape matters more than any single row: a per-lookup rate tracks your volume, so a marketing burst, a one-time list cleanse or a batch import of 50,000 records each draw down real money. A flat plan absorbs the same burst for the plan price.

A quoted Verify rate will differ from the Capture rate, possibly downward at commitment. It will still be per-lookup, and per-lookup still scales linearly.

What you are buying from each

Loqate covers 250 countries and territories, with Capture, Verify, email and phone validation, geocoding, maps and store-finder distances on one balance. If your traffic is genuinely global, that breadth is the product and it is not something a US-only tool can answer.

RevAddress is US-only and split in two, because the underlying data has two different owners.

Free, no postal license. Standardization, geocoding and address extract from unstructured text run against US Census Bureau address data. 1,000 requests a month, no card, no agreement to sign. This puts an address into correct form and returns coordinates. It does not tell you whether mail arrives.

DPV and the shipping endpoints, on your USPS license. ZIP+4, DPV confirmation, the CMRA, vacant and business flags, rates, service standards and tracking run against the USPS Addresses API using credentials you hold. You sign the USPS agreement and fund the Enterprise Payment Account; RevAddress manages the OAuth lifecycle, the caching, the rate-limit budgeting and the retries. The USPS API pricing guide covers the fee curve and the signature sequence, which runs on legal-department time.

If you cannot get a USPS agreement signed, that is a genuine reason to stay with a vendor that holds the data itself. Loqate is one.

For US addresses, side by side

The DPV code is the part worth understanding, because it is what makes a failure actionable. Y is deliverable. N is not. D means USPS found the building but needs an apartment or suite. S means the unit you sent is not one USPS recognizes. Those are four different bugs in a checkout form, and only the last two are the customer’s to fix.

The response

curl -X POST "https://api.revaddress.com/api/address/validate" \
-H "X-API-Key: rv_live_your_key" \
-H "Content-Type: application/json" \
-d '{
  "streetAddress": "1600 Pennsylvania Ave NW",
  "city": "Washington",
  "state": "DC",
  "ZIPCode": "20500"
}'

The body carries the standardized address, the DPV confirmation, and a resolution block naming what to do next.

{
"address": {
  "streetAddress": "1600 PENNSYLVANIA AVE NW",
  "city": "WASHINGTON",
  "state": "DC",
  "ZIPCode": "20500",
  "ZIPPlus4": "0005"
},
"additionalInfo": {
  "DPVConfirmation": "Y",
  "vacant": "N",
  "deliveryPoint": "00",
  "business": "Y"
},
"cached": false,
"resolution": {
  "classification": "deliverable_exact",
  "nextAction": "done",
  "userMessage": "USPS confirmed this address."
}
}

A D or S confirmation returns collect_secondary with a message that says USPS found the building but needs a unit number, so the form can ask for the right thing rather than showing a generic failure.

Field names accept aliases. street_address, address, address1, line1, zip, zip_code and postal_code all resolve, which removes the class of 400s caused by sending snake_case to a camelCase API.

Batch, and what it costs to re-run a list

Cleaning a mailing list is where per-lookup pricing bites hardest, because the second pass costs the same as the first. RevAddress hashes the normalized address and holds the result for 24 hours; a cached hit returns cached: true and does not draw your monthly allowance. Re-running the same list the same day is free.

Batch takes up to 50 addresses per call, settles each one independently so a single bad record cannot fail the request, and requires Growth or above. Free and Starter keys get a 403 with tier_required.

curl -X POST "https://api.revaddress.com/api/batch/validate" \
-H "X-API-Key: rv_live_your_key" \
-H "Content-Type: application/json" \
-d '{"addresses": [
  {"streetAddress": "1600 Pennsylvania Ave NW", "city": "Washington", "state": "DC"},
  {"streetAddress": "350 Fifth Avenue", "city": "New York", "state": "NY"}
]}'

Moving US validation off Loqate

This is not all-or-nothing. The usual shape is to route US traffic here and leave everything else on Loqate.

1. Get a free key at revaddress.com/signup. 1,000 requests a month, no card.
2. Decide which half you need. Standardization and geocoding work immediately. DPV needs your USPS credentials connected first, and getting the USPS agreement signed is the long pole.
3. Swap the call. Replace the Loqate Verify or Cleanse call with POST /api/address/validate.
4. Map the result. Use additionalInfo.DPVConfirmation and the resolution.nextAction field in place of Loqate’s match codes.
5. Move bulk jobs to POST /api/batch/validate, 50 per call, on Growth or above.
6. Keep Capture where it is if you rely on type-ahead. RevAddress has no equivalent.

Swapping the endpoint is a short job, usually an afternoon. Getting the USPS license signed is not, so start that first if DPV is on your list.

When to choose which

Loqate if you validate outside the US, if type-ahead at the point of entry is the feature you are actually buying, if you want email and phone validation on the same balance, or if you need a vendor that holds the postal data so you never sign with USPS.

RevAddress if your volume is US-centric, if you want a flat published price with no credit balance and no expiry, if standardization and geocoding are most of the job and free is the right price for them, or if you already hold USPS credentials and would rather not pay a second party to read data you are licensed for.

Sources

Loqate rates, credit expiry and trial terms come from the Loqate pricing page; the 250-country coverage figure and the Capture-versus-Verify descriptions come from Loqate’s address verification product page. Both were read on August 23, 2026 and both change without notice, so check them before you budget. RevAddress prices are on the pricing page; the batch limit, the plan gate and the cache duration are properties of the API itself.

Start here

• Free API key — 1,000 requests a month, no card, no USPS agreement
• Full pricing and the API reference with live try-it
• USPS API pricing in 2026 — the fee curve and what the license actually takes
• One file, not an integration? Clean a list from $19