shipapis
StarSubmit an APISubmit API

OpenCaged Geocoder (Open Source option) vs REST Countries

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

APIOpenCaged Geocoder (Open Source option)REACHABLE—REST CountriesHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedMPL-2.0
Free tierFree tier — API key requiredUnlimited
Rate limitUnpublishedNone published
In directory since2026-07-052026-05-02
operationalpartialdownno data

OpenCaged Geocoder (Open Source option) vs REST Countries: common questions

Which is more reliable, OpenCaged Geocoder (Open Source option) or REST Countries?

On our scheduled checks, REST Countries leads on measured uptime — OpenCaged Geocoder (Open Source option) at —% versus REST Countries 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 OpenCaged Geocoder (Open Source option) and REST Countries need an API key?

REST Countries needs no key, while OpenCaged Geocoder (Open Source option) requires a free API key. If you want to start calling without signup, reach for REST Countries first.

Can I call OpenCaged Geocoder (Open Source option) and REST Countries from the browser?

Yes — both OpenCaged Geocoder (Open Source option) and REST Countries 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 OpenCaged Geocoder (Open Source option) and REST Countries free for commercial use?

OpenCaged Geocoder (Open Source option) has unclear commercial terms, and REST Countries 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.