shipapis
StarSubmit an APISubmit API

LCBO vs Open Disease

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

APILCBOHEALTHY98Open DiseaseHEALTHY94
Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms207451
P95 · ms4291226
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (sources vary; see project repo)
Free tierFree — limits not publishedFree — no key required
Rate limit60 req/window · 59 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs Open Disease: common questions

Which is more reliable, LCBO or Open Disease?

On our scheduled checks, LCBO leads on measured uptime — LCBO at 100% versus Open Disease at 99.02% 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, LCBO or Open Disease?

LCBO has the lower median latency in our checks — LCBO responds in 207 ms versus Open Disease at 451 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 LCBO and Open Disease need an API key?

Neither needs a paid key — LCBO is callable with no signup, and Open Disease is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call LCBO and Open Disease from the browser?

Only Open Disease 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 Open Disease free for commercial use?

LCBO has unclear commercial terms, and Open Disease 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.