shipapis
StarSubmit an APISubmit API

OpenCaged Geocoder (Open Source option) vs Wikipedia REST

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

APIOpenCaged Geocoder (Open Source option)ON SCHEDULE—Wikipedia RESTHEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY-SA 4.0
Free tierFree tier — API key requiredUnlimited within etiquette
Rate limitUnpublished200/sec global courtesy cap
In directory since2026-07-052026-05-09
operationalpartialdownno data

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

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

Only Wikipedia REST is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do OpenCaged Geocoder (Open Source option) and Wikipedia REST need an API key?

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

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

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

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