Bevwire API vs Healthcare.gov

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedU.S. Government content (CMS)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs Healthcare.gov: common questions

Which is more reliable, Bevwire API or Healthcare.gov?

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

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

Can I call Bevwire API and Healthcare.gov from the browser?

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

Are Bevwire API and Healthcare.gov free for commercial use?

Bevwire API has unclear commercial terms, and Healthcare.gov 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.