shipapis
StarSubmit an APISubmit API

Healthcare.gov vs OpenF1

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

APIHealthcare.govHEALTHY92OpenF1DYING57
Uptime · 30d
Uptime · 90d96.1%47.1%
Uptime · 30d93.3%41.7%
P50 · ms420747
P95 · ms16963525
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseU.S. Government content (CMS)Unverified
Free tierFree — no key requiredFree & open (historical); real-time may require a free account
Rate limitUnpublishedRetry-After: 60s
In directory since2026-07-052026-07-05
operationalpartialdownno data

Healthcare.gov vs OpenF1: common questions

Which is more reliable, Healthcare.gov or OpenF1?

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

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

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

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

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

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