GeoApi vs HelloSalut

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

Uptime · 30d
Uptime · 90d97.8%97.8%
Uptime · 30d98.3%100%
P50 · ms4281457
P95 · ms28954778
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseLicence Ouverte (Etalab; INSEE/IGN data)Unverified
Free tierFree, no API keyFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GeoApi vs HelloSalut: common questions

Which is more reliable, GeoApi or HelloSalut?

Both are neck-and-neck — GeoApi and HelloSalut each measure 97.8% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, GeoApi or HelloSalut?

GeoApi has the lower median latency in our checks — GeoApi responds in 428 ms versus HelloSalut at 1457 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 HelloSalut need an API key?

Neither needs a paid key — GeoApi is callable with no signup, and HelloSalut is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call GeoApi and HelloSalut from the browser?

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

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