shipapis
StarSubmit an APISubmit API

24 Pull Requests vs CDNJS

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

API24 Pull RequestsHEALTHY90CDNJSHEALTHY95
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms678281
P95 · ms2785936
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree and open, no key
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs CDNJS: common questions

Which is more reliable, 24 Pull Requests or CDNJS?

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

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

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

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

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

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