The short answer
Google fits a component-verdict checkout flow inside Maps Platform; Smarty's US Street endpoint is a specialist option for US postal and secondary-unit analysis. Compare the actual postal evidence and missing-unit handling, not a geocode or an undifferentiated valid flag.
| Provider | A good reason to choose it | Important caveat |
|---|---|---|
| Google Address Validation | A checkout that needs component-level verdicts and a confirm-or-correct flow inside an existing Google Maps Platform integration. | Country coverage and billing SKU matter. US/PR CASS processing must be explicitly enabled; a response or coordinate alone does not establish delivery or identify an occupant. |
| Smarty | US address operations that need to inspect postal and secondary-unit evidence instead of accepting a normalized string as the only result. | US Street and International are different interfaces and entitlements. A returned candidate must be interpreted using its analysis fields; an empty candidate array is not an application transport error. |
Side-by-side differences
| Requirement | Google Address Validation | Smarty |
|---|---|---|
| Validation approach | Address component validation plus formatting and geocode | US postal-address candidates and analysis |
| Coverage boundary | Supported-country list; optional CASS only for US/PR | US Street endpoint; International is a separate product |
| Decision signal | Verdict granularity and component confirmation signals | Candidate and DPV-related analysis, not a single global score |
| Apartment/unit handling | Inspect subpremise and missing/unconfirmed component signals | Preserve street2 and interpret secondary-address evidence |
| Workflow | One address per validation request; confirm changes in the UI | Single-address GET or multi-address POST with server credentials |
| Cost driver | Validation request SKU, tier and Cloud project quota | Address lookups, product and licensed features |
Pricing: make the units comparable
| Provider | Billing model | What to check |
|---|---|---|
| Google Address Validation | Pay-as-you-go validation SKUs | Google documents per-request Pro and Enterprise SKUs and requires billing on the Cloud project. Check the actual SKU, included allowance and current region-specific pricing rather than reusing a Geocoding API price. |
| Smarty | Product-specific lookup subscriptions | Select US or International verification and the required feature/license tier. Batch requests contain multiple addresses; do not calculate price using only the number of HTTP requests. |
For 10,000 address checks, include retries and customer edits, not just completed orders. Count input addresses rather than batch HTTP calls. Compare the same country mix and postal evidence; a geocoding credit and a delivery-verification check do not buy the same result.
For a buying decision, calculate total spend divided by accepted outputs at your expected volume. Keep free evaluation access, paid production access, annual commitments and overages separate. We have not measured a cost or speed winner for this pair.
What changes in the integration?
| Google Address Validation | Smarty | |
|---|---|---|
| Method and URL | POST https://addressvalidation.googleapis.com/v1:validateAddress | GET https://us-street.api.smarty.com/street-address |
| Authentication | API key or supported OAuth token; restrict credentials to the intended API | Server-side auth-id and auth-token; embedded credentials have different restrictions |
| Inputs | JSON address with addressLines and recommended regionCode; optional enableUspsCass for US/PR | street, optional street2, city/state/zipcode, candidates and auth credentials; POST supports multiple addresses |
| Output | Validation result with verdict, address components, geocode and postal data where available; response identifier for follow-up. | Candidate array with components, metadata and postal analysis, including DPV-related fields where supplied. |
Google Address Validation: migration check
Map component confirmation and verdict fields rather than inventing one universal valid flag. Do not substitute the Geocoding API or silently enable CASS on arbitrary generated addresses.
Smarty: migration check
Handle zero, one and multiple candidates explicitly. Preserve leading-zero ZIP codes and separate missing-unit evidence from a street match; batch IDs must map back to original input records.
How to test them fairly
- Use provider-approved test fixtures or addresses you have permission to process. Include international formats, accents, rural addresses and unit numbers. Do not generate arbitrary postal addresses or send private customer records without authorization.
- Define expected outcomes for known-good records and approved negative cases before the run. Keep unsupported countries and missing evidence separate from invalid addresses.
- Measure component correction, unit preservation and false rejection separately. A geocoder's building-level match is not confirmation of postal deliverability or of the person living there.
- Record whether the API suggests a correction, confirms a delivery point or merely finds a location. Require customer confirmation when a suggested change could route a parcel elsewhere.
- Count billed address checks, repeated checkout attempts, optional geocoding and batch records. Compare latency and cost per accepted decision on the same country mix. No validation result guarantees a successful future delivery.
Record the plan, request settings, time window and acceptance rules with every run. That makes a later result interpretable when a vendor changes a model, source set or pricing tier.
Prefer a common request format?
POST /api/v1/address-validation/validateReview the request contract and tell us the coverage you need. Access requires enablement; this endpoint does not execute or bill requests yet.
View endpoint and request accessSources and review dates
Documentation reviewed October 28, 2026. These are integration and plan comparisons, not measured speed or accuracy rankings. Availability, licensing and prices should be confirmed for the chosen plan.
- Google Address Validation overview and coverage distinctions
- Google validation request and CASS option
- Google Address Validation billing
- Smarty US Street reference
- Smarty product pricing
Corrections: email faizank@docsalot.dev with an official source.