shipapis
StarSubmit an APISubmit API

Nominatim (OSM) vs Postcodes.io

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

APINominatim (OSM)HEALTHY—Postcodes.ioNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthuserAgentnone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial usenounclear
Data licenseODbL (OpenStreetMap)Service MIT-licensed; postcode data license unverified
Free tier1 req/sec, identified UA requiredFree — no key required
Rate limit1/sec hard — per applicationUnpublished (no key; fair use)
In directory since2026-05-022026-07-05
operationalpartialdownno data

Nominatim (OSM) vs Postcodes.io: common questions

Which is more reliable, Nominatim (OSM) or Postcodes.io?

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

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

Can I call Nominatim (OSM) and Postcodes.io from the browser?

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

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