Energy-Charts API vs OpenCaged Geocoder (Open Source option)

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Energy-Charts API vs OpenCaged Geocoder (Open Source option): common questions

Which is more reliable, Energy-Charts API or OpenCaged Geocoder (Open Source option)?

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

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

Can I call Energy-Charts API and OpenCaged Geocoder (Open Source option) from the browser?

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

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