Fruityvice vs LCBO
Same instrument, two spec sheets — measured, not claimed.
Fruityvice vs LCBO: common questions
Which is more reliable, Fruityvice or LCBO?
Both are neck-and-neck — Fruityvice 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, Fruityvice or LCBO?
LCBO has the lower median latency in our checks — Fruityvice responds in 951 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 Fruityvice and LCBO need an API key?
Neither needs a paid key — Fruityvice 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 Fruityvice and LCBO from the browser?
Neither sends browser-friendly CORS headers reliably, so call Fruityvice 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 Fruityvice and LCBO free for commercial use?
Fruityvice 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.