Smappee API vs ViaCep

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%98.3%
P50 · ms809651
P95 · ms16442277
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Smappee API vs ViaCep: common questions

Which is more reliable, Smappee API or ViaCep?

On our scheduled checks, Smappee API leads on measured uptime — Smappee API 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, Smappee API or ViaCep?

ViaCep has the lower median latency in our checks — Smappee API responds in 809 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 Smappee API and ViaCep need an API key?

ViaCep needs no key, while Smappee API requires a free API key. If you want to start calling without signup, reach for ViaCep first.

Can I call Smappee API and ViaCep from the browser?

Only ViaCep is browser-friendly — it returns CORS headers over HTTPS. Smappee API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Smappee API and ViaCep free for commercial use?

Smappee API 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.