shipapis
StarSubmit an APISubmit API

OpenCaged Geocoder (Open Source option) vs Shields

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

APIOpenCaged Geocoder (Open Source option)REACHABLE—ShieldsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenCaged Geocoder (Open Source option) vs Shields: common questions

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

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

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

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

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

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