shipapis
StarSubmit an APISubmit API

LCBO vs Open Food Facts

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

APILCBONEW—Open Food FactsNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit60 req/window · 59 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs Open Food Facts: common questions

Which is more reliable, LCBO or Open Food Facts?

On our scheduled checks, Open Food Facts leads on measured uptime — LCBO at —% versus Open Food Facts 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 LCBO and Open Food Facts need an API key?

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

Can I call LCBO and Open Food Facts from the browser?

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

LCBO has unclear commercial terms, and Open Food Facts 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.