shipapis
StarSubmit an APISubmit API

ES·pera API vs LAPIS

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

APIES·pera APIDYING37LAPISHEALTHY94
Uptime · 30d
Uptime · 90d0.0%100%
Uptime · 30d0.0%100%
P50 · ms—334
P95 · ms—1097
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree — no key (open instance)
Rate limitUnpublished
In directory since2026-09-212026-07-05
operationalpartialdownno data

ES·pera API vs LAPIS: common questions

Which is more reliable, ES·pera API or LAPIS?

On our scheduled checks, LAPIS leads on measured uptime — ES·pera API at 0.0% versus LAPIS at 100% 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 ES·pera API and LAPIS need an API key?

Neither needs a paid key — ES·pera API is callable with no signup, and LAPIS is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call ES·pera API and LAPIS from the browser?

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

Are ES·pera API and LAPIS free for commercial use?

ES·pera API has unclear commercial terms, and LAPIS 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.