shipapis
StarSubmit an APISubmit API

GeoApi vs Smappee API

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

APIGeoApiHEALTHY84Smappee APIHEALTHY89
Uptime · 30d
Uptime · 90d97.1%100%
Uptime · 30d95.0%100%
P50 · ms1016809
P95 · ms28621644
AuthnoneapiKey
CORSyesno
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 Smappee API: common questions

Which is more reliable, GeoApi or Smappee API?

On our scheduled checks, Smappee API leads on measured uptime — GeoApi at 97.1% versus Smappee API at 100% 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, GeoApi or Smappee API?

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

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

Can I call GeoApi and Smappee API from the browser?

Only GeoApi 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 GeoApi and Smappee API free for commercial use?

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