shipapis
StarSubmit an APISubmit API

eLife Sciences API vs IPinfo

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

APIeLife Sciences APINEW—IPinfoNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedKeyless /json works with limits; free token recommended (IPinfo Lite offers higher/unlimited access with a token)
Rate limitUnpublishedKeyless/unauthenticated access is rate-limited; numeric caps not stated on the developers page
In directory since2026-07-052026-07-05
operationalpartialdownno data

eLife Sciences API vs IPinfo: common questions

Which is more reliable, eLife Sciences API or IPinfo?

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

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

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

Yes — both eLife Sciences API and IPinfo send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are eLife Sciences API and IPinfo free for commercial use?

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