shipapis
StarSubmit an APISubmit API

Geocodify.com vs Open-Elevation API

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

APIGeocodify.comREACHABLE—Open-Elevation APINEW—
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

Geocodify.com vs Open-Elevation API: common questions

Which is more reliable, Geocodify.com or Open-Elevation API?

On our scheduled checks, Open-Elevation API leads on measured uptime — Geocodify.com at —% versus Open-Elevation API 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 Geocodify.com and Open-Elevation API need an API key?

Open-Elevation API needs no key, while Geocodify.com requires a free API key. If you want to start calling without signup, reach for Open-Elevation API first.

Can I call Geocodify.com and Open-Elevation API from the browser?

Yes — both Geocodify.com and Open-Elevation API 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 Geocodify.com and Open-Elevation API free for commercial use?

Geocodify.com has unclear commercial terms, and Open-Elevation API 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.