shipapis
StarSubmit an APISubmit API

LCBO vs openFDA

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

APILCBOHEALTHY98openFDAHEALTHY78
Uptime · 30d
Uptime · 90d100%94.1%
Uptime · 30d100%93.3%
P50 · ms2071187
P95 · ms4294661
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 openFDA: common questions

Which is more reliable, LCBO or openFDA?

On our scheduled checks, LCBO leads on measured uptime — LCBO at 100% versus openFDA at 94.1% 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, LCBO or openFDA?

LCBO has the lower median latency in our checks — LCBO responds in 207 ms versus openFDA at 1187 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 LCBO and openFDA need an API key?

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

Can I call LCBO and openFDA from the browser?

Only openFDA 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 openFDA free for commercial use?

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