From Address To Informed Action
Conceptual OverviewSubmitted Address
The address your customer enters.
Validation Response
Component signals, a verdict, and a geocode.
Choose An Action
Apply your rules to the response.
At A Glance
- Provides: Component validation, address standardization, and geocoding.
- Not: Identity verification, proof of residence, or a carrier delivery guarantee.
02 / What's Included
One Response, Several Kinds Of Evidence
Included
- Component-level confirmation (confirmed / plausible / suspicious)
- Standardized, formatted address output
- Bundled geocode — latitude/longitude in the same call
- Business, residential, and PO box detection
- CASS-certified USPS data for US & Puerto Rico
Not Included
- Identity / KYC verification of who lives there
- Guaranteed carrier deliverability
- Real-time NCOA move-updating
- Full postal metadata outside the ~40 supported countries
Confirmation Levels (Per Component)
Request Shape
03 / Why Google + USPS
Map And Postal Data In One Validation
Key Facts
- CASS™ certified (Coding Accuracy Support System) for US & Puerto Rico addresses
- geocode is returned with the validation result; inspect its granularity and coverage
- coverage in 40 countries and regions, growing as new markets move out of preview
Location and address context used by the service.
USPS-related processing for supported US and Puerto Rico addresses.
The validation response combines available evidence. Postal fields are conditional on geography and request.
04 / The Verdict Object
Not Pass/fail — A Confidence Signal You Can Branch On
Verdict Flags
- addressComplete — no unresolved tokens or unexpected/missing components; inspect confirmation signals separately
- hasUnconfirmedComponents / hasInferredComponents — what changed and why
- hasReplacedComponents / hasSpellCorrectedComponents — what Google fixed for you
Components and granularity meet your application's requirements.
Ask the user to review inferred, replaced, or uncertain components.
Request missing information or a corrected address before proceeding.
Illustrative application logic. possibleNextAction is a Preview field inside verdict; evaluate all relevant signals.
05 / Business, PO Box & USPS
Knowing What Kind Of Address It Is, Not Just Where It Is
Metadata Booleans
- business — flags a commercial address
- poBox — flags a PO box, not a street address
- residential — flags a home address
uspsData Fields (US & Puerto Rico)
06 / Extend With Maps Platform
A Clean Address Feeds Everything Downstream
Enable and authenticate each service for its own interface. APIs may use restricted keys or OAuth; BigQuery uses Google Cloud identity and dataset permissions, not an API key.
Pairs Well With
07 / Example Requests
A Clean Address Vs. One That Needs A Second Look
fully confirmed, standardized, and geocoded
POST https://addressvalidation.googleapis.com/v1:validateAddress
?key=YOUR_API_KEY
{ "address": { "regionCode": "US",
"addressLines": ["1600 Amphitheatre Pkwy",
"Mountain View, CA 94043"] } }
Illustrative output · No request executed
| Field | Value |
|---|---|
| verdict.addressComplete | true |
| address.formattedAddress | 1600 Amphitheatre Pkwy, Mountain View, CA 94043 |
| metadata.business | true |
| uspsData.dpvConfirmation | Y |
missing a unit number — flagged, not guessed
POST https://addressvalidation.googleapis.com/v1:validateAddress
?key=YOUR_API_KEY
{ "address": { "regionCode": "US",
"addressLines": ["100 Main St", "Springfield, IL"] } }
Illustrative output · No request executed
| Field | Value |
|---|---|
| verdict.addressComplete | false |
| verdict.hasUnconfirmedComponents | true |
| address.missingComponentTypes | subpremise |
| verdict.possibleNextAction | CONFIRM_ADD_SUBPREMISES |
08 / Use Cases And Industries
Where A Bad Address Becomes An Expensive Problem
Industries
09 / Reliability
Plan For Reliability And Recovery
The Commitment
- 99.9% monthly uptime objective for covered services
- Credits require eligibility, a timely claim, and the conditions in the SLA
The Proof
- Use the public status dashboard to investigate incidents
- Preview and Experimental features are subject to their own terms and exclusions
Inspect status and returned fields; missing data is not a successful business decision.
Use bounded retries and backoff for retryable failures; avoid retry storms.
Compare your logs with the public status dashboard and SLA claim requirements.
Availability and result quality are different measures.
10 / Coverage And Pricing
Price The Validation Workflow
Free Tier
- Pro: 5,000 validations free every month
- Enterprise: 1,000 validations free every month
At the listed global pay-as-you-go Pro rates, 1,000,000 total monthly requests cost $12,155: 5,000 free + 95,000 × $17/1,000 + 400,000 × $13.60/1,000 + 500,000 × $10.20/1,000. This example excludes discounts, taxes, and other usage.
| Monthly Volume | Pro / 1,000 | Enterprise / 1,000 |
|---|---|---|
| Free cap + 1 – 100,000 | $17.00 | $25.00 |
| 100,001 – 500,000 | $13.60 | $20.00 |
| 500,001 – 1,000,000 | $10.20 | $15.00 |
| 1,000,001 – 5,000,000 | $5.10 | $7.50 |
| 5,000,001+ | $1.28 | $2.28 |
Global USD list rates checked September 14, 2026. Pro: SKU A2E0-53FF-0BE3; Enterprise: SKU 10F3-119A-C6EC. Bands apply cumulatively after each SKU’s free allowance. Coverage includes 40 countries/regions; metadata is unavailable in Colombia, Italy, and Singapore, and India/Japan have Preview coverage. Confirm the current list before quoting.
11 / Get Started