LCBO vs SharpAPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limit60 req/window · 59 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs SharpAPI: common questions

Which is more reliable, LCBO or SharpAPI?

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

LCBO needs no key, while SharpAPI requires a free API key. If you want to start calling without signup, reach for LCBO first.

Can I call LCBO and SharpAPI from the browser?

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

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