shipapis
StarSubmit an APISubmit API

eLife Sciences API vs 24 Pull Requests

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

APIeLife Sciences APINEW—24 Pull RequestsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
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

eLife Sciences API vs 24 Pull Requests: common questions

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

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

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

Can I call eLife Sciences API and 24 Pull Requests 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 eLife Sciences API and 24 Pull Requests free for commercial use?

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