Foodish vs LCBO

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source)Unverified
Free tierFree — no keyFree — limits not published
Rate limitUnpublished60 req/window · 59 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Foodish vs LCBO: common questions

Which is more reliable, Foodish or LCBO?

On our scheduled checks, LCBO leads on measured uptime — Foodish 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 Foodish and LCBO need an API key?

Neither needs a paid key — Foodish 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 Foodish and LCBO from the browser?

Only Foodish 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 Foodish and LCBO free for commercial use?

Foodish 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.