shipapis
StarSubmit an APISubmit API

ISO 3166-2 API vs Nominatim (OSM)

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

APIISO 3166-2 APIUNMONITORED—Nominatim (OSM)HEALTHY—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneuserAgent
CORSnoyes
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-2 API vs Nominatim (OSM): common questions

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

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

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

Are ISO 3166-2 API and Nominatim (OSM) free for commercial use?

ISO 3166-2 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.