Global Shark Attack API vs npm Registry

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree (public registry)
Rate limitUnpublishedUnpublished (bulk scraping discouraged)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Global Shark Attack API vs npm Registry: common questions

Which is more reliable, Global Shark Attack API or npm Registry?

On our scheduled checks, npm Registry leads on measured uptime — Global Shark Attack API 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 Global Shark Attack API and npm Registry need an API key?

Neither needs a paid key — Global Shark Attack API is callable with no signup, and npm Registry is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Global Shark Attack API and npm Registry from the browser?

Yes — both Global Shark Attack API 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 Global Shark Attack API and npm Registry free for commercial use?

Global Shark Attack 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.