shipapis
StarSubmit an APISubmit API

DocForge vs JSONPlaceholder

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

APIDocForgeNEW—JSONPlaceholderNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished1000 req/window · 999 remaining · resets 1783509378
In directory since2026-07-052026-07-05
operationalpartialdownno data

DocForge vs JSONPlaceholder: common questions

Which is more reliable, DocForge or JSONPlaceholder?

On our scheduled checks, JSONPlaceholder leads on measured uptime — DocForge 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 DocForge and JSONPlaceholder need an API key?

Neither needs a paid key — DocForge is callable with no signup, and JSONPlaceholder is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call DocForge and JSONPlaceholder from the browser?

Only JSONPlaceholder is browser-friendly — it returns CORS headers over HTTPS. DocForge needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are DocForge and JSONPlaceholder free for commercial use?

DocForge 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.