ViaCep vs Zippopotam.us
Same instrument, two spec sheets — measured, not claimed.
ViaCep vs Zippopotam.us: common questions
Which is more reliable, ViaCep or Zippopotam.us?
On our scheduled checks, Zippopotam.us leads on measured uptime — ViaCep at 98.0% versus Zippopotam.us at 100% 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, ViaCep or Zippopotam.us?
Zippopotam.us has the lower median latency in our checks — ViaCep responds in 651 ms versus Zippopotam.us at 219 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 ViaCep and Zippopotam.us need an API key?
Neither needs a paid key — ViaCep is callable with no signup, and Zippopotam.us is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call ViaCep and Zippopotam.us from the browser?
Yes — both ViaCep and Zippopotam.us send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.
Are ViaCep and Zippopotam.us free for commercial use?
ViaCep has unclear commercial terms, and Zippopotam.us 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.