Nominatim (OSM) vs Ziptastic

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms332366
P95 · ms9902018
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 Ziptastic: common questions

Which is more reliable, Nominatim (OSM) or Ziptastic?

Both are neck-and-neck — Nominatim (OSM) and Ziptastic each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Nominatim (OSM) or Ziptastic?

Nominatim (OSM) has the lower median latency in our checks — Nominatim (OSM) responds in 332 ms versus Ziptastic at 366 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Nominatim (OSM) and Ziptastic need an API key?

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

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

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

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