Address Validation APIs: 6 providers, pricing and comparisons

Compare providers

6 providers, compared by integration fit rather than an untested score
Provider	Best fit	Billing model
Google Address Validation	A checkout that needs component-level verdicts and a confirm-or-correct flow inside an existing Google Maps Platform integration.	Pay-as-you-go validation SKUs
Smarty	US address operations that need to inspect postal and secondary-unit evidence instead of accepting a normalized string as the only result.	Product-specific lookup subscriptions
Loqate	A multinational address-data pipeline that needs country-aware cleansing, multiple input records and explicit quality codes.	Service-specific credits and account pricing
Geoapify	A location lookup or address-entry flow that can review ambiguous matches and does not require postal delivery-point confirmation.	Geocoding API credits and plan quotas
EasyPost	A shipping workflow already using EasyPost that needs verification results before proceeding to shipment and label operations.	Shipping-account and address-service pricing
Shippo	A checkout or shipping system that wants explicit address-change reasons before creating labels in the same platform.	Address Validation access and pricing through sales

The order is not a performance ranking. The right shortlist depends on the output, coverage and license you need.

Which workload are you building?

Define acceptance criteria before evaluating a provider
Workload	What to specify
Checkout address checks	Ask the customer to confirm material changes and supply missing units without blocking legitimate addresses solely on a confidence threshold.
Address-list cleanup	Country-specific parsing, batch correlation, preserved original records and separate matched, corrected, ambiguous and unsupported outcomes.
Pre-shipment validation	A shipping-address check before label creation, with carrier/country coverage and verification failure handled separately from API transport success.

Every provider comparison

Choose a pair for a side-by-side feature table, endpoint differences, cost considerations and migration notes.

Google Address Validation vs Smarty Google Address Validation vs Loqate Geoapify vs Google Address Validation EasyPost vs Google Address Validation Google Address Validation vs Shippo Loqate vs Smarty Geoapify vs Smarty EasyPost vs Smarty Shippo vs Smarty Geoapify vs Loqate EasyPost vs Loqate Loqate vs Shippo EasyPost vs Geoapify Geoapify vs Shippo EasyPost vs Shippo

USPS address validation API: current endpoints and alternatives

Compare cost on the same unit

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.

What can change the bill
Provider	Price and allowance check
Google Address Validation	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	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.
Loqate	Confirm the Address Verify entitlement, per-address consumption and optional geocoding. An address-capture lookup price is not automatically the price of a batch cleansing record.
Geoapify	Compare the applicable geocoding credits, rate limits and attribution rules. A cheaper location match is not a like-for-like substitute for postal verification when delivery evidence is required.
EasyPost	Confirm standalone address verification, international AVS and carrier-grade access on your account. Free label allowances or tracking prices are not standalone validation prices.
Shippo	Shippo directs Address Validation API pricing and access inquiries to sales. Do not substitute shipping-label fees or assume the standalone v2 service is included in an existing token's entitlement.

How to evaluate the shortlist

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.

Use a common endpoint contract

All Them APIs · Address Validation APIsPOST /api/v1/address-validation/validate

Review 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 access

Sources 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.

Corrections: email faizank@docsalot.dev with an official source.