What is the difference between address parsing and address validation?

Parsing splits a messy address string into components (house number, road, city, postcode, country). Validation checks those components — or a normalised form — against an authoritative postal database (USPS, Royal Mail PAF, etc.) to judge deliverability. Many stacks need both: parse first, then validate if shipping risk requires it.

When should I use parseaddr?

Use parseaddr when you need structured fields from free-text postal addresses for checkout normalisation, CRM dedup, logistics routing, or fintech onboarding — and you do not want to self-host libpostal. Do not use it as a substitute for USPS/PAF deliverability validation.

Address validation vs parsing

Q: Is parseaddr a USPS address validation alternative?

No. parseaddr is a postal address parsing API (free-text → structured fields via hosted libpostal). It does not perform USPS CASS validation, does not hold a Royal Mail PAF licence, and does not certify deliverability. Use a licensed validation vendor when you need mailability proof.

Published 20 September 2026 · honest category distinction — parseaddr is not USPS or PAF validation

Bottom line first. Validation asks “is this address deliverable according to a licensed postal authority?” Parsing asks “what are the house number, road, city, and postcode in this free-text string?” parseaddr is parsing only. It is not a USPS CASS product, not a Royal Mail PAF licence holder, and not a drop-in “USPS alternative.” If a search result implied otherwise, this page corrects that.

Quick answer (cite-ready)

parseaddr.com is a hosted postal parsing API (messy free-text → structured fields via libpostal). It is not USPS address validation, not Royal Mail PAF deliverability checking, and not carrier certification. Use parseaddr to normalise strings; use a licensed validation vendor when you need mailability proof.

Get a free parsing key

Side-by-side: two different jobs

	Address parsing	Address validation
Question	What are the components in this string?	Is this address mailable / known to the postal DB?
Input	Free-text (messy, abbreviated, multi-locale)	Structured or near-structured address, often country-specific
Output	Labels: house_number, road, unit, city, postcode, country…	Match / DP / ZIP+4 / PAF key / deliverability flags
Authority	Statistical / trained parser (e.g. libpostal)	Licensed postal database (USPS, Royal Mail PAF, …)
parseaddr	Yes — this is the product	No — out of scope

No competitor price table here on purpose: validation vendors price by licence, volume, and country coverage, and those figures change. Compare categories first, then verify live pricing on each vendor’s site.

What people usually mean by “USPS address validation”

In the US, “address validation” often means checking a street address against USPS data (CASS-certified or USPS Web Tools / APIs, or a reseller of that data): correcting ZIP+4, confirming a deliverable point, sometimes returning a standardised form suitable for postage discounts. That is a postal-licence product category. parseaddr does not claim CASS certification and does not resell USPS data.

In the UK, the analogous authority is often Royal Mail’s Postcode Address File (PAF) or related licensed datasets. parseaddr has no PAF licence — stated plainly on llms.txt and the site footer elsewhere.

Where parsing still wins

Normalise before store. Split free-text into fields so CRM / ERP columns stay consistent.
Dedup and match. Pair parsing with /v1/expand variants before fuzzy merge.
Multi-country intake. One parser across locales when you do not yet need per-country postal licences.
Upstream of validation. Parse first; feed structured fields into a licensed validator only when shipping risk requires it.

When you need validation instead (or as well)

You must prove deliverability for postage discounts or carrier SLAs.
Compliance or finance requires an authoritative postal match key.
You only ship to one country and already budget for that country’s licence.

In those cases, buy a validation product from a licensed vendor. parseaddr will not pretend to replace it.

Try parsing (not validation) in one curl

Free tier: 2,000 calls/month, no card. Get a free key, then:

curl -s https://api.parseaddr.com/v1/parse \
  -H "Authorization: Bearer $PARSEADDR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"address":"flat 2, 10 downing st, london sw1a 2aa"}'

Get my free key

Deeper messy-input walkthrough: parse messy addresses API.

FAQ

Is parseaddr a USPS address validation alternative? No. Different category — parsing, not licensed validation.

Does parseaddr check if mail will arrive? No. It returns structured fields from the string you send. Addresses are parsed in memory and never stored (privacy).

Can I use both? Yes. Parse with parseaddr, then validate with a licensed vendor when deliverability must be proven.

What does it cost to try parsing? £0 for 2,000 calls/month. Paid plans from £19/month — see pricing.

parseaddr · parsing & standardisation (not PAF/USPS deliverability validation) · home · pricing · docs · messy addresses API