Healthcare.gov vs NPPES

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useyesyes
Data licenseU.S. Government content (CMS)U.S. Government (public NPI data)
Free tierFree — no key requiredFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Healthcare.gov vs NPPES: common questions

Which is more reliable, Healthcare.gov or NPPES?

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

Neither needs a paid key — Healthcare.gov 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 Healthcare.gov and NPPES from the browser?

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

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