shipapis
StarSubmit an APISubmit API

LCBO vs LAPIS

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

APILCBOUNMONITORED—LAPISNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
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

LCBO vs LAPIS: common questions

Which is more reliable, LCBO or LAPIS?

Only LAPIS is on our probe schedule so far (—% uptime over 90 days). The other is catalogued but not yet live-checked, so we can't compare measured reliability head-to-head — check the uncovered API's own status page for now.

Do LCBO and LAPIS need an API key?

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

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

Are LCBO and LAPIS free for commercial use?

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