Skip to main content
All products
Live

Address Standardization API

Clean, standardized, structured addresses in 10ms.

Accuracy
99.5%
p99 latency
10ms
Uptime SLA
99.99%
curl -X POST https://api.goodvat.com/v1/address/normalize \
  -H "Authorization: Bearer $GOODVAT_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "query": "781 Franklin Ave Crown Heights Brooklyn NYC NY 11216 USA"
  }'
const response = await fetch("https://api.goodvat.com/v1/address/normalize", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.GOODVAT_API_KEY}`,
    "Content-Type": "application/json",
  },
  body: JSON.stringify({
    query: "781 Franklin Ave Crown Heights Brooklyn NYC NY 11216 USA",
  }),
});

const address = await response.json();
import os
import requests

response = requests.post(
    "https://api.goodvat.com/v1/address/normalize",
    headers={"Authorization": f"Bearer {os.environ['GOODVAT_API_KEY']}"},
    json={
        "query": "781 Franklin Ave Crown Heights Brooklyn NYC NY 11216 USA",
    },
)

address = response.json()
{
  "houseNumber": "781",
  "road": "Franklin Avenue",
  "suburb": "Crown Heights",
  "cityDistrict": "Brooklyn",
  "state": "NY",
  "postcode": "11216",
  "country": "USA",
  "expansions": [
    "781 franklin avenue crown heights brooklyn ny 11216 usa",
    "781 franklin avenue crown heights brooklyn new york 11216 usa"
  ]
}

Overview

What is Address Standardization?

Turn messy, free-form address strings into structured components and canonical token expansions, parsed, standardized, and ready for CRM dedup and MDM matching in 10ms.

A production-grade parsing and standardization engine trained on a vast, continuously growing dataset of global address and street-map data, covering every region GoodVat serves, not just English-speaking markets. Built on a heavily customized libpostal core combining Conditional Random Field (CRF) sequence labeling with a statistical multi-lingual token expansion engine, it extracts granular structured components (house number, road, unit, postcode, city, state, country) while generating canonical string expansions (resolving abbreviations like "St" → "Street", "Ave" → "Avenue", "Ste" → "Suite", directionals, and locale variations). An AI resolution layer steps in on the gnarliest inputs, such as incomplete addresses, colloquial descriptions, and formats no rules-based parser has seen before, all at single-digit-millisecond latency for instant deduplication, search indexing, and tax mapping.

What actually matters

Compliance teams don’t switch tools for a longer feature list — they switch for these.

Canonical token expansions

Delivers both discrete fields and fully expanded canonical string variants ("St" → "Street", "Ave" → "Avenue", "Ste" → "Suite", "NY" → "New York"), giving you turnkey search suggestions and exact deduplication keys.

CRF sequence labeling

Treats address parsing as a sequence-labeling problem rather than brittle regex templates, understanding addresses across 60+ languages and scripts.

Deterministic deduplication

Collapse duplicate customer, CRM, and listing records instantly by hashing or joining on canonical string expansions.

A match key for MDM & data matching

Canonical expansions are a ready-made key for master data management (MDM) and data matching pipelines. Deterministic record linkage instead of brittle fuzzy matching gives you a golden record and single customer view across CRM, ERP, and billing systems.

Hosted libpostal without the overhead

Get all the power of libpostal without managing 2GB model files in RAM, cold-start latency, or compilation bottlenecks. Fully managed with a 99.99% SLA.

Single-digit millisecond latency

A stateless engine running at a 10ms p99 latency — fast enough to run inline on every form field, search input, and checkout flow.

Flat, transparent pricing

$5/month for unlimited requests. No per-request metering or surprise overage bills.

Global multi-lingual coverage

Trained on worldwide street networks, handling transliterations, non-Latin scripts, and country-specific addressing conventions.

How it works

1

Parse anything

Free-form strings, out-of-order fields, missing components, mixed scripts and languages — parsed into structured house number, street, unit, city, region, postcode, and country.

2

Canonical token expansions

Standardizes abbreviations ("St" → "Street", "Ave" → "Avenue", "Ste" → "Suite", "N" → "North"), delivering canonical string variants ready for search suggestions, deduplication, and database indexing.

3

AI-assisted resolution

When statistical parsing alone is ambiguous — a missing unit number, a transliterated street name, an address described rather than written — an AI layer resolves it using context, not just pattern-matching.

4

Built for scale

A stateless, horizontally-scaled service engineered for a 10ms p99 and a 99.99% uptime SLA, so you can call it inline on every checkout, signup, and import.

5

Language & country aware

Pass an optional language and country hint to sharpen results, or let the model infer them. Global street-map coverage keeps output locale-correct.

Real-world use cases

Teams reach for Address Standardization for very different reasons. Here’s what that looks like in practice.

Search suggestions & indexing

Index canonical expanded variations so typeahead search matches regardless of whether a user types "st", "street", "ave", or "avenue".

CRM & data hygiene

Dedupe customer and account records where the same address was typed five different ways across your CRM, ERP, or support tool using canonical expansion keys.

Master data management (MDM)

Feed standardized, canonical addresses into your MDM or data matching platform as a reliable match key — the foundation for a golden record and single customer view across every system that stores an address.

Checkout & shipping

Clean customer-entered addresses and standardize street types before a shipping label is printed — fewer failed deliveries, fewer "address not found" support tickets.

Real estate & listings

Merge property listings and MLS feeds scraped from multiple sources by matching on standardized canonical strings.

Accurate tax jurisdiction

Standardize a billing address first so downstream tax calculation resolves the right state, county, and city. Garbage in, wrong tax out.

KYC & fraud detection

Standardize address format during signup and onboarding so identity checks, proof-of-address documents, and fraud ring detection compare apples to apples.

Pricing

Live pricing, straight from the API.

Custom Requirements

Looking for something else?

If our standard tiers don't match your volume, data residency, SLA, or custom workflow requirements — we'd love to talk. We're always happy to listen and tailor solutions for your team.

FAQ

Frequently asked questions

More questions, answered

Start with what’s live today

Get an API key and make your first standardized address in minutes. $5 a month, unlimited requests, no card games.