shipapis
StarSubmit an APISubmit API

ISO 3166 Updates API vs Nominatim (OSM)

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

APIISO 3166 Updates APIUNMONITORED—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

ISO 3166 Updates API vs Nominatim (OSM): common questions

Which is more reliable, ISO 3166 Updates API 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 ISO 3166 Updates API and Nominatim (OSM) need an API key?

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

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

ISO 3166 Updates API 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.