shipapis
StarSubmit an APISubmit API

LAPIS vs Lexigram

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

APILAPISNEW—LexigramNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); UnverifiedUnverified
Free tierFree — no key (open instance)Free tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LAPIS vs Lexigram: common questions

Which is more reliable, LAPIS or Lexigram?

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

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

Can I call LAPIS and Lexigram from the browser?

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

Are LAPIS and Lexigram free for commercial use?

LAPIS has unclear commercial terms, and Lexigram 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.