shipapis
StarSubmit an APISubmit API

Healthcare.gov vs LCBO

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

APIHealthcare.govHEALTHY92LCBOHEALTHY98
Uptime · 30d
Uptime · 90d96.1%100%
Uptime · 30d93.3%100%
P50 · ms420207
P95 · ms1696429
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseU.S. Government content (CMS)Unverified
Free tierFree — no key requiredFree — limits not published
Rate limitUnpublished60 req/window · 59 remaining · resets 60
In directory since2026-07-052026-07-05
operationalpartialdownno data

Healthcare.gov vs LCBO: common questions

Which is more reliable, Healthcare.gov or LCBO?

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

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

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

Can I call Healthcare.gov and LCBO from the browser?

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

Are Healthcare.gov and LCBO free for commercial use?

Healthcare.gov allows commercial use on its free tier, and LCBO 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.