24 Pull Requests vs JSONPlaceholder

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms678401
P95 · ms27851096
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

24 Pull Requests vs JSONPlaceholder: common questions

Which is more reliable, 24 Pull Requests or JSONPlaceholder?

Both are neck-and-neck — 24 Pull Requests and JSONPlaceholder each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, 24 Pull Requests or JSONPlaceholder?

JSONPlaceholder has the lower median latency in our checks — 24 Pull Requests responds in 678 ms versus JSONPlaceholder at 401 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do 24 Pull Requests and JSONPlaceholder need an API key?

Neither needs a paid key — 24 Pull Requests 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 24 Pull Requests and JSONPlaceholder from the browser?

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

Are 24 Pull Requests and JSONPlaceholder free for commercial use?

24 Pull Requests 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.