shipapis
StarSubmit an APISubmit API

Bevwire API vs LAPIS

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

APIBevwire APIDYING75LAPISHEALTHY94
Uptime · 30d
Uptime · 90d71.1%100%
Uptime · 30d13.3%100%
P50 · ms477334
P95 · ms19001097
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree — limits not publishedFree — no key (open instance)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs LAPIS: common questions

Which is more reliable, Bevwire API or LAPIS?

On our scheduled checks, LAPIS leads on measured uptime — Bevwire API at 71.1% 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.

Which is faster, Bevwire API or LAPIS?

LAPIS has the lower median latency in our checks — Bevwire API responds in 477 ms versus LAPIS at 334 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Bevwire API and LAPIS need an API key?

Neither needs a paid key — Bevwire 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 Bevwire API and LAPIS from the browser?

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

Are Bevwire API and LAPIS free for commercial use?

Bevwire 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.