GeoApi vs Zipcodestack

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseLicence Ouverte (Etalab; INSEE/IGN data)Unverified
Free tierFree, no API keyFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoApi vs Zipcodestack: common questions

Which is more reliable, GeoApi or Zipcodestack?

On our scheduled checks, Zipcodestack leads on measured uptime — GeoApi at —% versus Zipcodestack at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do GeoApi and Zipcodestack need an API key?

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

Can I call GeoApi and Zipcodestack from the browser?

Yes — both GeoApi and Zipcodestack 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 GeoApi and Zipcodestack free for commercial use?

GeoApi allows commercial use on its free tier, and Zipcodestack 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.