Google Address Validation Alternatives: Cost at Volume

Google's Address Validation API includes 5,000 free billable events a month on the Pro SKU (Google calls this a free usage cap; billing must still be enabled), then bills $17 per 1,000 successful requests for usage through 100,000 requests. On standard pay-as-you-go pricing, 100,000 requests a month cost $1,615 and 1 million about $12,155. Google's Pro subscription plan can lower those figures, as shown below. Teams look at alternatives when volume grows, when they need to keep results longer than Google's 30-day caching limit, or when they only need US addresses.

We are sthan.io, one of the vendors compared here. Every underlying price below comes from the vendor's own public pricing page, read on the date shown. Where a figure is calculated from a published plan and overage rate, we label it as our calculation. Prices change, so check the source before you decide.

Cost at 10K, 100K and 1M lookups a month

Pricing note: these figures are not perfectly like for like. Google's standard pay-as-you-go pricing meters billable events (successful requests on Pro, Autocomplete (New) sessions that end in validation on Enterprise); its subscription plans are covered below. sthan.io and Smarty sell monthly capacity, PostGrid adds overage to a plan, and Radar sells annual commitments priced by quote. Where a vendor's plan does not match the exact volume, we use the smallest published plan that covers it rather than interpolating a hypothetical price; figures marked with an asterisk are our own calculations from published rates, included for directional comparison only. Prices checked September 28, 2026.

* PostGrid: $475 and $4,975 extrapolate the published Growth plan ($225 for 50,000 lookups plus $0.005 per extra lookup); PostGrid does not publish a plan at those volumes. Radar: figures multiply its published starting rate of $2 per 1,000 API calls; Radar sells annual commitments priced by quote, not monthly plans at these volumes.

Google's lower rates apply only to the requests inside each band: $17 per 1,000 up to 100,000, then $13.60 for the next 400,000, then $10.20. That is how 1 million lands near $12,155. More vendors and pricing models: how address verification APIs are priced.

Google's subscription plans change the math above 76,000 a month

Google also sells fixed monthly subscription plans that cover several Maps Platform products with one combined call limit. Google's plan table marks Address Validation Pro as included in the Pro plan only: $1,200 a month for 250,000 combined calls. The $100 Starter and $275 Essentials plans do not include it. Calls above the limit are billed at standard pay-as-you-go rates, and Google sets that overage rate by your total monthly usage.

On pay-as-you-go, $1,200 buys about 76,000 Address Validation requests, so above roughly that volume the Pro subscription is the cheaper way to buy Google, if its 250,000-call allowance is not also used by other Maps Platform APIs. The allowance is shared across every product in the plan, so the break-even point depends on what else your billing account uses.

What Google includes

• A verdict with fields such as addressComplete, validationGranularity, hasUnconfirmedComponents and possibleNextAction.
• A corrected address and a geocode in the same response.
• Optional USPS CASS processing for US and Puerto Rico addresses. Google says the API is confirmed as a CASS-Certified service. CASS processing is opt-in: set enableUspsCass to true in the request, and Google says the flag affects only the uspsData field. Google also says uspsData is not guaranteed to be fully populated for every address, and recommends checking the verdict and address fields as well.
• 40 listed countries and regions on Google's coverage page as of September 28, 2026, with India and Japan in preview. It is not global.
• Two SKUs for two billing workflows. The same Address Validation API sits behind both. Pro bills each successful validation request. Enterprise bills Autocomplete (New) sessions that end in a validation request.

Terms worth reading before you build

• Caching. Google's service terms allow caching the formatted address, postal address, component names and USPS standardized address for 30 consecutive calendar days, and only to reuse them in that end user's own later transactions. Component correction flags get 30 days for correction requests, and coordinates get 30 days for any purpose. After 30 days you must delete the cached data or replace it with what the end user confirmed. If you need to store corrected addresses for longer, read Google's service-specific terms first.
• Do not send artificially created US or Puerto Rico addresses. Google's service terms say that if a customer does, Google will stop validating that customer's addresses with USPS services, and will report the customer's name and address, the input address and aggregated usage data to USPS.

When to stay with Google, and when to switch

Sources

All read September 28, 2026: developers.google.com/maps/documentation/address-validation (requests-validate-address, understand-response, coverage, validateAddress reference), developers.google.com/maps/billing-and-pricing (pricing, sku-details, subscriptions), cloud.google.com/maps-platform/terms/maps-service-terms (Address Validation API section: artificially-created addresses, caching table). Other vendors: sthan.io/pricing/united-states, postgrid.com/pricing-address-verification, smarty.com/pricing/us-address-verification, radar.com/pricing.