shipapis
StarSubmit an APISubmit API

Cutt.ly vs GitHub Project Issues

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

APICutt.lyNEW—GitHub Project IssuesNEW—
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 GitHub Project Issues: common questions

Which is more reliable, Cutt.ly or GitHub Project Issues?

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

GitHub Project Issues needs no key, while Cutt.ly requires a free API key. If you want to start calling without signup, reach for GitHub Project Issues first.

Can I call Cutt.ly and GitHub Project Issues from the browser?

Neither sends browser-friendly CORS headers reliably, so call Cutt.ly and GitHub Project Issues 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 GitHub Project Issues free for commercial use?

Cutt.ly has unclear commercial terms, and GitHub Project Issues 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.