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