Google Address Validation API Pricing: The Per-Request Cost (and the Flat-Rate USPS Alternative)

If you’re validating US addresses, Google’s Address Validation API is the obvious first stop — it’s Google, the docs are good, and you can be making calls in ten minutes. For low volume on a mapping or geocoding workflow, it’s a reasonable choice.

But two things catch teams off guard once they ship: the per-request bill scales linearly with volume, and the API is not full USPS CASS-certified — which matters the moment you need deliverability accuracy or postal discounts, not just a pin on a map.

RevAddress takes the opposite approach: a flat monthly fee on top of the authoritative USPS v3 Addresses API. Here’s the honest comparison, with the math.

What Google’s Address Validation API actually costs

Google reorganized Maps Platform pricing on March 1, 2025. The old flat $200/month credit is gone — replaced by per-SKU free monthly call caps plus optional subscription tiers. Address Validation is classified as a “Pro” SKU, which gets 5,000 free calls per month. After that:

Google Maps Platform pricing as of June 2026. The free tier is per-SKU, not a shared dollar credit.

So the free tier covers light usage, but the per-request rate kicks in hard once you pass it. Here’s what that means in dollars per month versus RevAddress’s flat plans:

The crossover is around 10,000 validations/month. Below that, Google’s free tier is genuinely cheaper — we’ll say that plainly. Above it, Google’s bill climbs $17 per thousand while RevAddress stays flat. At 50K validations a month — a single mid-size mailing list cleaned once — you’re looking at roughly $765 on Google versus $79 on RevAddress, and the gap widens every month you grow.

If your volume lives under 5,000/month and you only need geocoding-grade validation, stay on Google’s free tier. This post is for everyone above that line.

The bigger gap: CASS certification

Pricing is the visible problem. Deliverability is the one that bites later.

Google’s Address Validation API validates addresses for mapping and geocoding — its goal is to put a correct point on a map. It is not full USPS CASS-certified. That distinction matters more than it sounds:

• No CASS Form 3553. Presort and bulk-mail postage discounts require CASS-certified output. Google can’t produce it, so you can’t claim the discount.
• No guaranteed DPV confirmation. Delivery Point Validation tells you an address is a real, deliverable USPS delivery point — not just a plausible-looking string. Google validates plausibility, not USPS deliverability.
• Geocode-valid ≠ deliverable. Google can return a “valid” address that USPS won’t deliver to (and occasionally reject one USPS happily delivers to), because the two systems optimize for different things.

RevAddress sits directly on the USPS v3 Addresses API — the postal service’s own authoritative source. You get USPS-standardized output, DPV-grade deliverability signals, and the canonical ZIP+4 the Postal Service itself uses to route mail. For anything touching physical mail, shipping, or postal discounts, that’s the difference between “looks right” and “USPS will deliver it.”

Side-by-side: the request

The migration is a straight swap — both are JSON-over-HTTPS POST calls. The shapes differ slightly, but there’s no rewrite.

curl -X POST \
"https://addressvalidation.googleapis.com/v1:validateAddress?key=$GOOGLE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "address": {
    "regionCode": "US",
    "addressLines": ["1600 Pennsylvania Ave NW"],
    "locality": "Washington",
    "administrativeArea": "DC"
  }
}'

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

RevAddress also accepts field-name aliases — street_address, address1, line1, zip, zip_code all resolve to the right field, so you won’t get a 400 because your payload used snake_case. And for the common case of cleaning a list, batch validation runs up to 50 addresses per call with Promise.allSettled semantics: one bad address never fails the whole batch.

A caching footnote that costs real money

Google Maps Platform’s Terms of Service restrict how long you may cache or store results from most SKUs. If you’re cleaning the same customer list or re-validating repeat checkout addresses, you’re often re-paying to re-validate addresses you already validated.

RevAddress ships a 24-hour KV cache included in every plan — repeat addresses inside the window don’t count against your quota and don’t cost anything. Re-running last week’s mailing list is free the second time.

Migration checklist

1. Get an API key. Sign up — 1,000 validations/month free, no card required.
2. Swap the endpoint. Replace addressvalidation.googleapis.com/v1:validateAddress with https://api.revaddress.com/api/validate. Move the key from the ?key= query param to the X-API-Key header.
3. Flatten the payload. Google nests under address: { addressLines: [...] }; RevAddress takes top-level streetAddress / city / state (aliases accepted).
4. Read deliverability from the response. Use the USPS-standardized address and DPV/deliverability fields instead of Google’s verdict object. See the API reference.
5. Switch list-cleaning jobs to batch. POST /api/batch/validate, up to 50 per call, fault-isolated — see the batch validation guide.

Proof points

• Built directly on the USPS v3 Addresses API — the postal authority’s own data, not a third-party approximation.
• 500+ tests across 29 suites; webhooks, batch validation, and BYOK in production.
• Flat monthly pricing — no per-lookup surcharges, no surprise overage bills.
• 24-hour caching included — repeat addresses are free.
• BYOK — bring your own USPS credentials on Pro and Enterprise.

When Google is still the right call

No bashing — here’s where Google genuinely wins:

• You need global coverage. RevAddress is US-only via USPS. Google validates 240+ regions. For international addresses, look at Google, Loqate, or PostGrid.
• You’re geocoding, not mailing. If you need lat/lng for a map and never touch physical delivery, Google’s mapping stack is the natural fit.
• You stay under 5,000/month. The free tier is real. Below the crossover, Google costs you nothing.

When to switch to RevAddress

• You validate more than ~10,000 US addresses a month and want a predictable, flat bill.
• You need USPS-grade deliverability — DPV confirmation, CASS-clean output, true ZIP+4.
• You send physical mail or packages and care about postal discounts and delivery rates.
• You re-validate repeat addresses and want caching that doesn’t re-bill you.
• You’d rather call one USPS-native API than wire address validation to a mapping product.

The bottom line

Google’s Address Validation API is a fine geocoding tool with a usable free tier. But it bills per request, it caps how you cache, and it isn’t full USPS CASS-certified — so at volume, or anywhere mail actually has to arrive, you’re paying more for less deliverability certainty. If you’re US-focused and doing more than a few thousand validations a month, RevAddress’s flat, USPS-native plan is both cheaper and more accurate where it counts.