Choose an address validation API by the decision your checkout or customer-record process must make: accept the address, ask the customer to confirm a correction, or route an exception to a person. Smarty offers detailed US address metadata and non-postal coverage. Loqate separates address capture from verification with a global focus. Melissa combines postal validation with broader address-data options. Google Address Validation API exposes structured verdicts and component evidence. Lob connects verification to a wider mail operation. A recognized location is not the same thing as a complete postal delivery address.
What the buying decision includes
Define the delivery countries, carriers, apartment or suite requirements and treatment of newly built or non-postal addresses. Apply the same acceptance policy to every provider: which fields must be verified, which corrections need confirmation, and what happens when evidence is incomplete? Type-ahead assistance, verification of a submitted address and geocoding are separate services with different billing. The goal is a controlled customer-record decision; no returned coordinate or vendor accuracy headline proves that a specific shipment will arrive.
| Service | Reason to shortlist | Commercial distinction | Acceptance boundary |
|---|---|---|---|
| Smarty | US secondary-unit and detailed address evidence | Submitted-address lookups; subscription renewal | Non-postal existence versus USPS delivery |
| Loqate | Capture and verify across countries | Capture and Verify have distinct credit costs | Country and sub-premise depth |
| Melissa | Postal data with wider maintenance options | Confirm API, deployment and enrichments | Postal checks versus extra appended data |
| Google Address Validation API | Structured verdict and correction signals | Pay-per-request validation SKU | Completeness, components and granularity together |
| Lob | Verification beside an automated mail program | US versus international verification packages | Verification purchase versus print/postage |
Smarty
Smarty US Address Verification provides metadata including delivery-point match codes, residential/business indicators and secondary-address information. It also recognizes non-postal addresses outside USPS delivery data. Its pricing FAQ counts each submitted address as a lookup, whether sent individually or in a batch; the autocomplete API uses a different counting model. The page permits retaining previously validated US verification data after the subscription ends, with a separate restriction for rooftop geocoding data. Smarty official source.
Shortlist Smarty for a US workflow needing explicit apartment and postal-versus-non-postal distinctions. Recognizing a rural location can help a private-carrier delivery, but should not silently override a USPS-only mailing policy. Configure that distinction rather than treating every recognized address as equivalent. Review renewal behavior too: depleted plans can return payment-required errors unless renewal is arranged, and renewing an exhausted annual block starts a new annual period. A batch cleanup can therefore pull forward another subscription purchase instead of a simple overage bill. Smarty official source.
Loqate
Loqate separates Address Capture from Address Verify. Its verification offering describes global coverage, transliteration and premise/sub-premise data; depth still needs to be confirmed for the countries involved. The current US pricing page gives distinct credit costs for Capture and Verify, with larger prepaid purchases lowering the lookup rate. Credits are valid for 12 months and published prices exclude VAT. Bespoke plans offer additional commercial and support scope. Loqate official source.
Consider Loqate when customers enter addresses in several countries and the team wants capture assistance alongside verification. Keep those functions separate in the forecast: successful type-ahead entry is not evidence that a later record-validation request is free or unnecessary. Specify the expected countries, scripts and apartment behavior, then price each operation. Older indexed pricing describes Verify as price-on-application, whereas the current directly retrieved US page publishes credit rates; confirm the current regional offer rather than mixing the two versions. Loqate official source.
Melissa
Melissa presents address validation across more than 250 countries, with postal formatting, parsing and transliteration. Its US offering describes DPV, LACSLink and SuiteLink data, plus optional capabilities such as AddressPlus and non-USPS address data. It also distinguishes Express Entry autocomplete from verification and offers cloud or on-premises choices. The overview directs buyers to a pricing discussion rather than establishing one universal API subscription. Melissa official source.
Shortlist Melissa when address quality extends beyond checkout into data maintenance or postal operations. The buying task is to identify the specific product and enrichments required: access to a vendor portfolio does not mean every dataset is bundled. An organization needing only validation should not compare a broad data-quality proposal with another provider single-purpose API rate. Ask which result codes and secondary-address functions are included for each country, how updates are supplied, and who operates the chosen deployment. Appended information still needs an acceptance policy. Melissa official source.
Google Address Validation API
Google separates the validation verdict from the formatted address, component details, geocode and optional metadata. Its documentation recommends evaluating the verdict first, then using the rest of the response to inform correction or confirmation. Validation granularity can differ from geocode granularity: an apartment can be validated even when its geographic point represents the building. USPS-specific output applies to US and Puerto Rico addresses. The API is billed per request with billing enabled on the project. Google Address Validation API official source.
This is useful when an application team wants to implement a visible accept, confirm or correct decision in its own interface. Do not collapse the response into a single universal confidence percentage. Confirm supported countries, applicable storage/display terms and the current validation SKU rather than borrowing the price of Google geocoding or autocomplete. Quotas control requests, but do not define your customer-service fallback when an otherwise valuable order has an incomplete address. That fallback remains a product decision. Google Address Validation API official source.
Lob
Lob publishes separate US and international address-verification allowances and additional-use rates alongside its wider direct-mail packages. The current pricing body distinguishes verification charges from print and postage, and offers custom enterprise terms. Its introductory direct-mail platform price is therefore not a complete statement of verification usage. The live page uses different labels in some cards and comparison columns, so the contracted package needs to be identified explicitly. Lob official source.
Consider Lob when address validation will support a mail program already being coordinated through Lob, or when its verification proposal fits the application independently. Cost the required US and international mix separately, then confirm whether the verification purchase stands alone or depends on a platform package. Mailing pieces, validated addresses and application users are different quantities. Do not infer that an allowance for one is included in another, and do not use the cheapest printed-mail price as an API lookup price. Lob official source.
Which purchase fits your operation?
For a US workflow requiring detailed postal and secondary-unit evidence, compare Smarty with the precise Melissa product proposed. For multi-country capture plus verification, examine Loqate operation costs and country depth. For application-owned confirmation logic, examine Google response semantics and terms. For an integrated mail operation, scope Lob verification separately from print and postage. Use the same exception policy across the shortlist so a broader match does not automatically look like a better answer.
A missing apartment, a recognized non-postal address and a corrected house number deserve different customer interactions. Decide those interactions before choosing the API. Preserve the original customer input alongside the approved correction as appropriate for the business, and assign an owner to unresolved records. A provider can supply evidence; the organization still decides when that evidence is sufficient to accept the address.
For related decisions, compare geocoding APIs for coordinates and match evidence and shipping software for the fulfillment workflow after address acceptance.
By Toolverly Editorial, with AI-assisted research and drafting. Product information checked November 3, 2026.
Photo by SumUp on Unsplash. Read about our publication or send a correction.