shipapis
StarSubmit an APISubmit API

Cutt.ly vs VerifyEd

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

APICutt.lyNEW—VerifyEdNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthapiKeyapiKey
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key requiredFree tier — API key required
Rate limitUnpublished100 req/window · 99 remaining · resets 1783522020
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cutt.ly vs VerifyEd: common questions

Which is more reliable, Cutt.ly or VerifyEd?

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

Both ask you to authenticate — Cutt.ly uses an API key and VerifyEd 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 VerifyEd from the browser?

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

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