DiscGolf vs NPPES

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms762910
P95 · ms21532071
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseFree to use with attribution (per response metadata)U.S. Government (public NPI data)
Free tierFree — public endpoints, no keyFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

DiscGolf vs NPPES: common questions

Which is more reliable, DiscGolf or NPPES?

Both are neck-and-neck — DiscGolf and NPPES each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, DiscGolf or NPPES?

DiscGolf has the lower median latency in our checks — DiscGolf responds in 762 ms versus NPPES at 910 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 DiscGolf and NPPES need an API key?

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

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

Are DiscGolf and NPPES free for commercial use?

DiscGolf has unclear commercial terms, 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.