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.
| parseaddr | Smarty | |
|---|---|---|
| Primary job | Parse / standardise free-text into fields | Validate & autocomplete against postal data |
| Engine | Hosted libpostal (~1B training addresses) | Licensed USPS / international datasets |
| Free tier | 2,000 calls/month, no card | Limited trial; sales-led for volume |
| Self-serve GBP pricing | £19 / £99 / £399 hard caps | Enterprise / list pricing typical |
| Agent path | MCP + signup/checkout/topup APIs | REST SDKs; less agent-native buy path |
| Deliverability licence | No (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.
house_number, road, unit, city, postcode, country).POST /v1/parse with the original free-text (not the already-validated string if you still have it).