shipapis
StarSubmit an APISubmit API

LCBO vs TheCocktailDB

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

APILCBOHEALTHY98TheCocktailDBHEALTHY77
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms207300
P95 · ms429562
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit60 req/window · 59 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs TheCocktailDB: common questions

Which is more reliable, LCBO or TheCocktailDB?

Both are neck-and-neck — LCBO and TheCocktailDB each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, LCBO or TheCocktailDB?

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

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

Can I call LCBO and TheCocktailDB from the browser?

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

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