shipapis
StarSubmit an APISubmit API

Nominatim (OSM) vs PostalCodes

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

APINominatim (OSM)HEALTHY—PostalCodesNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthuserAgentnone
CORSyesno
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 PostalCodes: common questions

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

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

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

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

Only Nominatim (OSM) is browser-friendly — it returns CORS headers over HTTPS. PostalCodes needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Nominatim (OSM) and PostalCodes free for commercial use?

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