The short answer
For a US-only postal workflow, start by examining Smarty's candidate and DPV-related analysis. For international batch cleansing, examine Loqate Verify's country-specific quality codes. Do not compare Smarty US Street coverage with Loqate's whole international product without matching the geography.
| Provider | A good reason to choose it | Important caveat |
|---|---|---|
| Loqate | A multinational address-data pipeline that needs country-aware cleansing, multiple input records and explicit quality codes. | Capture suggestions are not Verify results. Pin the endpoint version and interpret Address Verification Codes in the relevant country context instead of comparing them numerically with another provider's confidence score. |
| 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 | Loqate | Smarty |
|---|---|---|
| Validation approach | Country-aware Address Verify cleansing | US postal-address candidates and analysis |
| Coverage boundary | International country coverage and data depth vary | US Street endpoint; International is a separate product |
| Decision signal | AVC and match/quality details need interpretation | Candidate and DPV-related analysis, not a single global score |
| Apartment/unit handling | Country-specific sub-building and address components | Preserve street2 and interpret secondary-address evidence |
| Workflow | Single or batch input through International Batch Cleanse | Single-address GET or multi-address POST with server credentials |
| Cost driver | Input addresses, service credit rules and optional enrichment | Address lookups, product and licensed features |
Pricing: make the units comparable
| Provider | Billing model | What to check |
|---|---|---|
| Loqate | Service-specific credits and account pricing | 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. |
| 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?
| Loqate | Smarty | |
|---|---|---|
| Method and URL | POST https://api.addressy.com/Cleansing/International/Batch/v1.20/json6.ws | GET https://us-street.api.smarty.com/street-address |
| Authentication | Loqate Key scoped to the selected service | Server-side auth-id and auth-token; embedded credentials have different restrictions |
| Inputs | JSON Key, Addresses array with country/address components; optional GeoCode and processing options | street, optional street2, city/state/zipcode, candidates and auth credentials; POST supports multiple addresses |
| Output | Per-input match records and normalized fields with quality information such as AVC; optional geocoding output. | Candidate array with components, metadata and postal analysis, including DPV-related fields where supplied. |
Loqate: migration check
Pin v1.20/json6 or your contracted version and map quality codes using official definitions. Keep Capture's Find/Retrieve workflow out of a Verify adapter and preserve per-record identifiers in a batch.
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.
- Loqate International Batch Cleanse reference
- Loqate Address Verify overview
- Smarty US Street reference
- Smarty product pricing
Corrections: email faizank@docsalot.dev with an official source.