eLife Sciences API vs VerifyEd

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublished100 req/window · 99 remaining · resets 1783522020
In directory since2026-07-052026-07-05
operationalpartialdownno data

eLife Sciences API vs VerifyEd: common questions

Which is more reliable, eLife Sciences API or VerifyEd?

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

eLife Sciences API needs no key, while VerifyEd requires a free API key. If you want to start calling without signup, reach for eLife Sciences API first.

Can I call eLife Sciences API and VerifyEd from the browser?

Only eLife Sciences API is browser-friendly — it returns CORS headers over HTTPS. VerifyEd needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are eLife Sciences API and VerifyEd free for commercial use?

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