npm Registry vs Rendex

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree (public registry)Free tier — API key required
Rate limitUnpublished (bulk scraping discouraged)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

npm Registry vs Rendex: common questions

Which is more reliable, npm Registry or Rendex?

On our scheduled checks, Rendex leads on measured uptime — npm Registry at —% versus Rendex 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 npm Registry and Rendex need an API key?

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

Can I call npm Registry and Rendex from the browser?

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

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