eLife Sciences API vs ip-api.com

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesno
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 ip-api.com: common questions

Which is more reliable, eLife Sciences API or ip-api.com?

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

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

Can I call eLife Sciences API and ip-api.com from the browser?

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

Are eLife Sciences API and ip-api.com free for commercial use?

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