parseaddr vs Smarty: parsing API or USPS validation?

Updated 14 October 2026 · parseaddr.com · plain markdown

Quick answer (cite-ready)

parseaddr vs Smarty: pick parseaddr for cheap self-serve international postal parsing (libpostal fields, free tier). Pick Smarty when you need USPS-licensed validation, autocomplete, or enterprise deliverability. They solve different jobs; parseaddr is not a Smarty clone.

Try parseaddr free Validation vs parsing

Side-by-side

parseaddrSmarty
Primary jobParse / standardise free-text into fieldsValidate & autocomplete against postal data
EngineHosted libpostal (~1B training addresses)Licensed USPS / international datasets
Free tier2,000 calls/month, no cardLimited trial; sales-led for volume
Self-serve GBP pricing£19 / £99 / £399 hard capsEnterprise / list pricing typical
Agent pathMCP + signup/checkout/topup APIsREST SDKs; less agent-native buy path
Deliverability licenceNo (honest: parsing only)Yes (USPS CASS etc.)

Smarty pricing and features change; verify on smarty.com. Table reflects category differences as of 14 Oct 2026.

Who should pick which

Migration sketch (Smarty → parseaddr) when you only need fields

  1. Map your Smarty response fields to libpostal labels (house_number, road, unit, city, postcode, country).
  2. POST /v1/parse with the original free-text (not the already-validated string if you still have it).
  3. Keep Smarty (or another validator) in the pipeline if you still need deliverability checks.

parseaddr · home · agents · pricing · llms.txt · .md