shipapis
StarSubmit an APISubmit API

OpenCaged Geocoder (Open Source option) vs Voidly

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

APIOpenCaged Geocoder (Open Source option)REACHABLE—VoidlyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedCC BY 4.0
Free tierFree tier — API key requiredFree (keyless data endpoints; Hydra ML endpoints need a key)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

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

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

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

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

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

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

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