shipapis
StarSubmit an APISubmit API

Cutt.ly vs Icanhazip

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

APICutt.lyDEAD0IcanhazipDEAD0
Uptime · 30d
Uptime · 90d0.0%0.0%
Uptime · 30d0.0%0.0%
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 Icanhazip: common questions

Which is more reliable, Cutt.ly or Icanhazip?

Both are neck-and-neck — Cutt.ly and Icanhazip each measure 0.0% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Do Cutt.ly and Icanhazip need an API key?

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

Can I call Cutt.ly and Icanhazip from the browser?

Only Icanhazip 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 Icanhazip free for commercial use?

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