shipapis
StarSubmit an APISubmit API

Cutt.ly vs 24 Pull Requests

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

APICutt.lyUNMONITORED—24 Pull RequestsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeynone
CORSnono
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 24 Pull Requests: common questions

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

Only 24 Pull Requests is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do Cutt.ly and 24 Pull Requests 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 Cutt.ly and 24 Pull Requests from the browser?

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

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

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