shipapis
StarSubmit an APISubmit API

24 Pull Requests vs eLife Sciences API

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

API24 Pull RequestsNEW—eLife Sciences APINEW—
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 limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

24 Pull Requests vs eLife Sciences API: common questions

Which is more reliable, 24 Pull Requests or eLife Sciences API?

On our scheduled checks, eLife Sciences API leads on measured uptime — 24 Pull Requests at —% versus eLife Sciences API 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 24 Pull Requests and eLife Sciences API need an API key?

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

Can I call 24 Pull Requests and eLife Sciences API from the browser?

Only eLife Sciences API 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 eLife Sciences API free for commercial use?

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