shipapis
StarSubmit an APISubmit API

Bevwire API vs LCBO

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

APIBevwire APIHEALTHY89LCBOHEALTHY98
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms701207
P95 · ms1900429
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublished60 req/window · 59 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs LCBO: common questions

Which is more reliable, Bevwire API or LCBO?

Both are neck-and-neck — Bevwire API and LCBO 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, Bevwire API or LCBO?

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

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

Can I call Bevwire API and LCBO from the browser?

Neither sends browser-friendly CORS headers reliably, so call Bevwire API and LCBO from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are Bevwire API and LCBO free for commercial use?

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