US Address Parser API

Address parser API that splits any US address into fields

One REST call breaks a raw address line into house number, street, unit, city, state, and ZIP. Built for developers.

✓ 3,000 requests/month free ✓ $8/mo for 10,000 lookups ✓ No credit card
Try it · live
Paste a raw address
Match mode

Returns the address split into fields. Check matchTier and confidence.

- ms 0 used today 500 left today

Got a whole list? Upload the file and clean every row →

One call, every field

What comes back

Each parse returns the address split into clean components, plus the match metadata to trust it.

fullAddress
addressNumber
streetName
streetPostType
streetPostDir
unitType
unitNumber
city
stateCode
zipCode
zip4
county
matchTier
confidence
Built for real-world input

What it reads and cleans up

Raw address strings are messy. Here is what the parser resolves, with real examples.

Misspelled streets and cities

1345 avvenue of americas new york ny → 1345 Avenue Of The Americas, New York, NY 10105-0302
6000 j street sacrmento ca → 6000 J St, Sacramento, CA 95819-2605

Missing state or ZIP

543 sanders road cross → 543 Sanders Rd, Cross, SC 29436
1199 w shaw avenue fresno → 1199 W Shaw Ave, Fresno, CA 93711

Abbreviations and unit types

325 w broaddwey # m ny 10013 → 325 W Broadway PH M, New York, NY 10013-1835
standardizes St, Ave, Blvd, Apt, Suite, #

Out-of-order lines

1345 americas avenue NY → 1345 Ave Of The Americas, New York, NY 10105-0302
1199 fresno avenue west shaw ca → 1199 W Shaw Ave, Fresno, CA 93711

Measured, not claimed: on 26,943 corrupted real US addresses (August 2026 benchmark) the parser recovered the right address 96.2% of the time on single typos or dropped fields and 99.9% on formatting-only damage, and refused to guess 99.9% of the time when the house number did not exist. Full results by damage type in the accuracy benchmark; the test method is published so you can run it on any vendor.

Where teams use it

Common use cases

Clean CRM & user dataSplit freeform address fields into columns before you store or dedupe them.
Prep shipping labelsTurn a single typed line into the street, city, state, and ZIP your carrier expects.
Normalize importsStructure messy spreadsheet or form data on the way into your database.
Feed downstream checksParse first, then send clean components to verification or geocoding.
Copy, paste, ship

A single GET request

Send a raw address, get structured JSON back. No SDK required.

Request
# raw input, one call
curl "https://api.sthan.io/v2/address-parser/usa/speculative/1600%20pennsylvania%20ave%20nw%20washington%20dc%2020500" \
  -H "Authorization: Bearer YOUR_API_KEY"
Response
{
  "inputAddress": "1600 pennsylvania ave nw washington dc 20500",
  "fullAddress": "1600 Pennsylvania Ave NW, Washington, DC 20500-0005",
  "addressLine1": "1600 Pennsylvania Ave NW",
  "addressLine2": "Washington, DC 20500-0005",
  "addressNumber": "1600",
  "streetPreDir": null,
  "streetPreType": null,
  "streetName": "Pennsylvania",
  "streetPostType": "Ave",
  "streetPostDir": "NW",
  "unitType": null,
  "unitNumber": null,
  "city": "Washington",
  "stateCode": "DC",
  "state": "District Of Columbia",
  "zipCode": "20500",
  "zip4": "0005",
  "county": "District Of Columbia",
  "matchMode": "Speculative",
  "matchTier": "Exact",
  "confidence": 1,
  "matchCode": {
    "houseNumber": "Matched",
    "street": "Matched",
    "unit": "NotApplicable",
    "city": "Matched",
    "state": "Matched",
    "zipCode": "Matched",
    "zip4": "Inferred"
  },
  "matchedFromCache": false,
  "isError": false
}
Simple pricing

Start free, scale when you need to

Monthly plans, billed by request volume. Annual saves up to 50%.

Start here
Free
$0
3,000 requests / month
No credit card
Basic
$8 /mo
10,000 requests
Starter
$28 /mo
50,000 requests
Business
$58 /mo
150,000 requests

Higher volumes and annual discounts (up to 50%) on the plans page.

Good to know

Questions developers ask

What is address parsing?

Breaking a single address string into its parts: house number, street name and type, unit, city, state, ZIP and ZIP+4, so you can store, sort, and integrate structured fields.

How is this different from verification?

The parser splits a raw string into fields. Verification also checks the address against postal data and returns a deliverable status. Many teams parse first, then verify.

Does it handle messy input?

Yes. It reads typos, abbreviations, missing parts, and out-of-order lines, and returns clean structured fields instead of an empty result.

How fast is a parse?

Complete addresses typically return in 1 to 5 seconds. Partial or ambiguous input can take longer while it applies deeper recovery.

What do I need to get started?

An email address. Sign up, grab your API key, and send your first request. The free tier gives you 3,000 requests a month (up to 100 a day) with no card on file.

Parse your first address in two minutes

Sign up, copy your key, make the call. 3,000 requests a month, free.

Get your free API key