shipapis
StarSubmit an APISubmit API

Healthcare.gov vs LAPIS

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

APIHealthcare.govNEW—LAPISNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseU.S. Government content (CMS)Open sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree — no key requiredFree — no key (open instance)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Healthcare.gov vs LAPIS: common questions

Which is more reliable, Healthcare.gov or LAPIS?

On our scheduled checks, LAPIS leads on measured uptime — Healthcare.gov at —% versus LAPIS 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 Healthcare.gov and LAPIS need an API key?

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

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

Only LAPIS is browser-friendly — it returns CORS headers over HTTPS. Healthcare.gov needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Healthcare.gov and LAPIS free for commercial use?

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