Loqate vs RevAddress — Address Verification Pricing and API Compared (2026)

Loqate (a GBG solution, formerly PCA Predict / Postcode Anywhere) is one of the most established address verification providers in the world. Its coverage spans 240+ countries and territories, and if you’re cleaning international addresses across dozens of markets, it’s a serious tool.

But most US-based teams don’t need 240 countries. They need one country done well — validated to USPS standards, priced predictably, and running fast at checkout. That’s where Loqate’s model starts to cost more than it should: verification is billed per-lookup, in credits, behind a sales quote, and the global data footprint you’re paying into is one you may never touch.

RevAddress takes the opposite approach for US addresses: flat monthly pricing on the USPS v3 REST layer — DPV-confirmed validation, batch processing, and the rest of the USPS stack included. Here’s the honest comparison.

The pricing model is the real difference

The single most important thing to understand about Loqate is that it does not publish a flat per-lookup price. As of July 2026, Loqate’s verification pricing is credit-based and quote-driven — you create an account, buy credit packs, and each address lookup consumes credits. Volume discounts exist (larger commitments lower the per-lookup rate), but the published path to a real number runs through a sales conversation, and credits can expire before you use them.

The problem with a per-lookup model isn’t the headline rate — it’s the shape of the bill. Your cost tracks your volume. A one-time mailing-list cleanse, a marketing campaign, or a batch import of 50,000 records all draw down credits. On a flat plan, that same burst costs exactly what the plan costs.

What that looks like in practice

Loqate publishes no rate, so take a volume-discounted $0.02 per lookup — the generous end for address verification at scale — and put it beside RevAddress’s real, published flat tiers looks like this:

Your quoted rate will differ by commitment and region, and it will still do the same thing: any per-lookup rate scales linearly while RevAddress stays flat, and the gap compounds at volume. RevAddress’s real pricing is public on the pricing page — no quote required.

What you are actually buying from Loqate

Loqate is a global capture platform: 240-country coverage, Capture+ typeahead, geocoding add-ons across many markets. Every one of those is priced into the credits whether your traffic uses them or not. A US checkout validating to USPS standards is paying for the world.

RevAddress is US-only by design and USPS-native, on one flat price. If you also validate outside the US, keep a global tool for those markets and route the US volume — usually most of it — here.

For US addresses: what RevAddress does that Loqate’s US path doesn’t

The USPS DPV distinction is worth calling out. RevAddress returns Delivery Point Validation codes on every response — Y (confirmed deliverable), N (not deliverable), D (missing secondary/apartment), S (invalid secondary). That tells you exactly why an address failed, which is what you need when you’re debugging why a package bounced.

Code comparison

RevAddress is a straight REST call with an API key header — no SDK required, no credit accounting to reason about.

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 response includes the DPV confirmation code, the standardized USPS-formatted address, and ZIP+4 — the things you actually act on:

{
"deliverable": true,
"dpvConfirmation": "Y",
"address": {
  "streetAddress": "1600 PENNSYLVANIA AVE NW",
  "city": "WASHINGTON",
  "state": "DC",
  "ZIPCode": "20500",
  "ZIPPlus4": "0003"
}
}

RevAddress also accepts field-name aliases — street_address, address1, line1, zip_code, zip all resolve — so you don’t get 400 errors for sending snake_case.

Batch validation without per-record billing

Cleaning a mailing list is where per-lookup pricing hurts most. On RevAddress, batch addresses count against your monthly cap, and cached repeats don’t count at all — so re-running the same list costs nothing the second time.

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"}
]}'

Each address is validated independently — one bad record never fails the whole batch.

Migration from Loqate (US validation)

If you’re moving your US address validation off Loqate — while keeping Loqate for international if you need it:

1. Sign up at revaddress.com/signup — free, 1,000 lookups/mo, no card.
2. Swap the endpoint — replace your Loqate Verify/Cleanse call with POST /api/address/validate (see above).
3. Map the result — use dpvConfirmation (Y/N/D/S) instead of Loqate’s AVC/match codes.
4. Move bulk jobs to POST /api/batch/validate — no per-record credit draw.
5. Prove it with the free key before switching production traffic.
6. Keep Loqate for non-US markets if your product needs them — this isn’t all-or-nothing.

Typical migration time for US-only validation: 1–3 hours.

When to choose which

Choose Loqate if:

• You validate addresses outside the US (240+ countries — RevAddress can’t do this).
• You need hosted autocomplete/typeahead (Capture+).
• You need geocoding across many markets.

Choose RevAddress if:

• Your address volume is US-centric.
• You want flat, published pricing with no sales quote and no credit accounting.
• You need USPS DPV codes, batch with fault isolation, or address extraction.
• You want validation plus the full USPS shipping stack under one key.
• You want to stop paying into global coverage you don’t use.

The bottom line

Loqate is an excellent global address platform. If you’re international, get a quote — it’s the right tool. But for US-focused teams, its per-lookup, credit-based, sales-gated model means you pay for scale you can predict and coverage you don’t use. RevAddress gives you USPS-native validation at a flat monthly rate you can read off a page today — and the crossover happens fast.

Related

• Smarty vs RevAddress — the other per-lookup address-validation comparison
• Melissa Address Verification Pricing — credit-math breakdown
• Google Address Validation API Pricing — per-request cost at scale
• Lob vs RevAddress — address validation without the direct-mail tax
• API Reference — interactive examples and live try-it