shipapis
StarSubmit an APISubmit API

API Reference - Ideal Postcodes vs Nominatim (OSM)

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

APIAPI Reference - Ideal PostcodesUNMONITORED—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

API Reference - Ideal Postcodes vs Nominatim (OSM): common questions

Which is more reliable, API Reference - Ideal Postcodes or Nominatim (OSM)?

Only Nominatim (OSM) is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do API Reference - Ideal Postcodes and Nominatim (OSM) need an API key?

Neither needs a paid key — API Reference - Ideal Postcodes 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 API Reference - Ideal Postcodes and Nominatim (OSM) from the browser?

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

API Reference - Ideal Postcodes 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.