CountryStateCity vs GeoApi

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

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

CountryStateCity vs GeoApi: common questions

Which is more reliable, CountryStateCity or GeoApi?

On our scheduled checks, GeoApi leads on measured uptime — CountryStateCity at —% versus GeoApi 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 CountryStateCity and GeoApi need an API key?

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

Can I call CountryStateCity and GeoApi from the browser?

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

CountryStateCity has unclear commercial terms, and GeoApi allows commercial use on its free tier. 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.