shipapis
StarSubmit an APISubmit API

Cutt.ly vs JSONPlaceholder

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

APICutt.lyNEW—JSONPlaceholderNEW—
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 limitUnpublished1000 req/window · 999 remaining · resets 1783509378
In directory since2026-07-052026-07-05
operationalpartialdownno data

Cutt.ly vs JSONPlaceholder: common questions

Which is more reliable, Cutt.ly or JSONPlaceholder?

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

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

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

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

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