shipapis
StarSubmit an APISubmit API

Cutt.ly vs ELI

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

APICutt.lyNEW—ELINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key may be required for production
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cutt.ly vs ELI: common questions

Which is more reliable, Cutt.ly or ELI?

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

Both ask you to authenticate — Cutt.ly uses an API key and ELI uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

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

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

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