shipapis
StarSubmit an APISubmit API

24 Pull Requests vs Cutt.ly

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

API24 Pull RequestsNEW—Cutt.lyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs Cutt.ly: common questions

Which is more reliable, 24 Pull Requests or Cutt.ly?

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

24 Pull Requests needs no key, while Cutt.ly requires a free API key. If you want to start calling without signup, reach for 24 Pull Requests first.

Can I call 24 Pull Requests and Cutt.ly from the browser?

Neither sends browser-friendly CORS headers reliably, so call 24 Pull Requests and Cutt.ly from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are 24 Pull Requests and Cutt.ly free for commercial use?

24 Pull Requests has unclear commercial terms, and Cutt.ly 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.