24 Pull Requests vs SampleAPIs

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms678471
P95 · ms2785984
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished5000 req/window · 3876 remaining · resets 1783516346
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs SampleAPIs: common questions

Which is more reliable, 24 Pull Requests or SampleAPIs?

Both are neck-and-neck — 24 Pull Requests and SampleAPIs 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 SampleAPIs?

SampleAPIs has the lower median latency in our checks — 24 Pull Requests responds in 678 ms versus SampleAPIs at 471 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 SampleAPIs need an API key?

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

Can I call 24 Pull Requests and SampleAPIs from the browser?

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

24 Pull Requests has unclear commercial terms, and SampleAPIs 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.