PostalCodes vs ViaCep
Same instrument, two spec sheets — measured, not claimed.
PostalCodes vs ViaCep: common questions
Which is more reliable, PostalCodes or ViaCep?
On our scheduled checks, PostalCodes leads on measured uptime — PostalCodes at 99.02% versus ViaCep at 98.0% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, PostalCodes or ViaCep?
ViaCep has the lower median latency in our checks — PostalCodes responds in 1030 ms versus ViaCep at 651 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.
Do PostalCodes and ViaCep need an API key?
Neither needs a paid key — PostalCodes is callable with no signup, and ViaCep is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call PostalCodes and ViaCep from the browser?
Only ViaCep is browser-friendly — it returns CORS headers over HTTPS. PostalCodes needs a server-side call or proxy, so factor that into which one fits a front-end project.
Are PostalCodes and ViaCep free for commercial use?
PostalCodes has unclear commercial terms, and ViaCep has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.