ISO 3166 Updates API vs Nominatim (OSM)
Same instrument, two spec sheets — measured, not claimed.
ISO 3166 Updates API vs Nominatim (OSM): common questions
Which is more reliable, ISO 3166 Updates API or Nominatim (OSM)?
Both are neck-and-neck — ISO 3166 Updates API and Nominatim (OSM) each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.
Which is faster, ISO 3166 Updates API or Nominatim (OSM)?
Nominatim (OSM) has the lower median latency in our checks — ISO 3166 Updates API responds in 1402 ms versus Nominatim (OSM) at 332 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.
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.