shipapis
StarSubmit an APISubmit API

LCBO vs NPPES

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

APILCBONEW—NPPESNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedU.S. Government (public NPI data)
Free tierFree — limits not publishedFree — no key required
Rate limit60 req/window · 59 remaining · resets 60Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LCBO vs NPPES: common questions

Which is more reliable, LCBO or NPPES?

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

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

Can I call LCBO and NPPES from the browser?

Neither sends browser-friendly CORS headers reliably, so call LCBO and NPPES 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 NPPES free for commercial use?

LCBO has unclear commercial terms, and NPPES allows commercial use on its free tier. 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.