Foodish vs LCBO
Same instrument, two spec sheets — measured, not claimed.
Foodish vs LCBO: common questions
Which is more reliable, Foodish or LCBO?
On our scheduled checks, LCBO leads on measured uptime — Foodish at 27.5% versus LCBO at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.
Which is faster, Foodish or LCBO?
LCBO has the lower median latency in our checks — Foodish responds in 250 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 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?
Neither sends browser-friendly CORS headers reliably, so call Foodish 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 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.