shipapis
StarSubmit an APISubmit API

BigDataCloud Geocode vs Nominatim (OSM)

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

APIBigDataCloud GeocodeNEW—Nominatim (OSM)HEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneuserAgent
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearno
Data licenseUnverifiedODbL (OpenStreetMap)
Free tierFree — limits not published1 req/sec, identified UA required
Rate limitUnpublished1/sec hard — per application
In directory since2026-07-052026-05-02
operationalpartialdownno data

BigDataCloud Geocode vs Nominatim (OSM): common questions

Which is more reliable, BigDataCloud Geocode or Nominatim (OSM)?

On our scheduled checks, Nominatim (OSM) leads on measured uptime — BigDataCloud Geocode at —% versus Nominatim (OSM) 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 BigDataCloud Geocode and Nominatim (OSM) need an API key?

Neither needs a paid key — BigDataCloud Geocode is callable with no signup, and Nominatim (OSM) is keyless with a required User-Agent header. Both are quick to prototype with; rate limits still apply.

Can I call BigDataCloud Geocode and Nominatim (OSM) from the browser?

Yes — both BigDataCloud Geocode and Nominatim (OSM) 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 BigDataCloud Geocode and Nominatim (OSM) free for commercial use?

BigDataCloud Geocode has unclear commercial terms, and Nominatim (OSM) is personal/non-commercial only. 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.