Cutt.ly vs Global Shark Attack API

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cutt.ly vs Global Shark Attack API: common questions

Which is more reliable, Cutt.ly or Global Shark Attack API?

On our scheduled checks, Global Shark Attack API leads on measured uptime — Cutt.ly at —% versus Global Shark Attack API 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 Cutt.ly and Global Shark Attack API need an API key?

Global Shark Attack API needs no key, while Cutt.ly requires a free API key. If you want to start calling without signup, reach for Global Shark Attack API first.

Can I call Cutt.ly and Global Shark Attack API from the browser?

Only Global Shark Attack API is browser-friendly — it returns CORS headers over HTTPS. Cutt.ly needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Cutt.ly and Global Shark Attack API free for commercial use?

Cutt.ly has unclear commercial terms, and Global Shark Attack API 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.