shipapis
StarSubmit an APISubmit API

Cutt.ly vs Fake JSON API

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

APICutt.lyNEW—Fake JSON APINEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
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 Fake JSON API: common questions

Which is more reliable, Cutt.ly or Fake JSON API?

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

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

Can I call Cutt.ly and Fake JSON API from the browser?

Only Fake JSON API 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 Fake JSON API free for commercial use?

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