API Reference - Ideal Postcodes vs ViaCep
Same instrument, two spec sheets — measured, not claimed.
API Reference - Ideal Postcodes vs ViaCep: common questions
Which is more reliable, API Reference - Ideal Postcodes or ViaCep?
On our scheduled checks, API Reference - Ideal Postcodes leads on measured uptime — API Reference - Ideal Postcodes at 100% 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, API Reference - Ideal Postcodes or ViaCep?
API Reference - Ideal Postcodes has the lower median latency in our checks — API Reference - Ideal Postcodes responds in 154 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 API Reference - Ideal Postcodes and ViaCep need an API key?
Neither needs a paid key — API Reference - Ideal Postcodes 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 API Reference - Ideal Postcodes and ViaCep from the browser?
Yes — both API Reference - Ideal Postcodes and ViaCep 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 API Reference - Ideal Postcodes and ViaCep free for commercial use?
API Reference - Ideal Postcodes 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.