shipapis
StarSubmit an APISubmit API

Fruityvice vs LCBO

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

APIFruityviceNEW—LCBONEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API keyFree — limits not published
Rate limitUnpublished60 req/window · 59 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fruityvice vs LCBO: common questions

Which is more reliable, Fruityvice or LCBO?

On our scheduled checks, LCBO leads on measured uptime — Fruityvice at —% versus LCBO at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

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.