shipapis
StarSubmit an APISubmit API

npm Registry vs scrapestack

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

APInpm RegistryHEALTHY98scrapestackHEALTHY96
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms243346
P95 · ms1246844
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree (public registry)Free tier — key may be required
Rate limitUnpublished (bulk scraping discouraged)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

npm Registry vs scrapestack: common questions

Which is more reliable, npm Registry or scrapestack?

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

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

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

Can I call npm Registry and scrapestack from the browser?

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

Are npm Registry and scrapestack free for commercial use?

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