LCBO vs Lexigram

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

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

LCBO vs Lexigram: common questions

Which is more reliable, LCBO or Lexigram?

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

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

Can I call LCBO and Lexigram from the browser?

Neither sends browser-friendly CORS headers reliably, so call LCBO and Lexigram from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are LCBO and Lexigram free for commercial use?

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