shipapis
StarSubmit an APISubmit API

ELI vs npm Registry

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

APIELINEW—npm RegistryNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree (public registry)
Rate limitUnpublishedUnpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

ELI vs npm Registry: common questions

Which is more reliable, ELI or npm Registry?

On our scheduled checks, npm Registry leads on measured uptime — ELI at —% versus npm Registry at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do ELI and npm Registry need an API key?

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

Can I call ELI and npm Registry from the browser?

Yes — both ELI and npm Registry 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 ELI and npm Registry free for commercial use?

ELI 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.