Nominatim (OSM) vs Zippopotam.us

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthuserAgentnone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial usenounclear
Data licenseODbL (OpenStreetMap)Unverified
Free tier1 req/sec, identified UA requiredFree — limits not published
Rate limit1/sec hard — per applicationUnpublished
In directory since2026-05-022026-07-05
operationalpartialdownno data

Nominatim (OSM) vs Zippopotam.us: common questions

Which is more reliable, Nominatim (OSM) or Zippopotam.us?

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

Neither needs a paid key — Nominatim (OSM) is keyless but wants an identifying User-Agent header, and Zippopotam.us is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Nominatim (OSM) and Zippopotam.us from the browser?

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

Nominatim (OSM) is personal/non-commercial only, and Zippopotam.us 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.