shipapis
StarSubmit an APISubmit API

Geocoder REST API vs npm Registry

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

APIGeocoder REST APIHEALTHY90npm RegistryHEALTHY98
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms739243
P95 · ms13021246
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree (public registry)
Rate limitUnpublishedUnpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Geocoder REST API vs npm Registry: common questions

Which is more reliable, Geocoder REST API or npm Registry?

Both are neck-and-neck — Geocoder REST API and npm Registry 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, Geocoder REST API or npm Registry?

npm Registry has the lower median latency in our checks — Geocoder REST API responds in 739 ms versus npm Registry at 243 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 Geocoder REST API and npm Registry need an API key?

npm Registry needs no key, while Geocoder REST API requires a free API key. If you want to start calling without signup, reach for npm Registry first.

Can I call Geocoder REST API and npm Registry from the browser?

Only npm Registry is browser-friendly — it returns CORS headers over HTTPS. Geocoder REST API needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Geocoder REST API and npm Registry free for commercial use?

Geocoder REST API has unclear commercial terms, and npm Registry 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.