shipapis
StarSubmit an APISubmit API

Bevwire API vs NPPES

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

APIBevwire APIHEALTHY89NPPESHEALTHY89
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms701910
P95 · ms19002071
Authnonenone
CORSnono
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedU.S. Government (public NPI data)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bevwire API vs NPPES: common questions

Which is more reliable, Bevwire API or NPPES?

Both are neck-and-neck — Bevwire API 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, Bevwire API or NPPES?

Bevwire API has the lower median latency in our checks — Bevwire API responds in 701 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 Bevwire API and NPPES need an API key?

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

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

Bevwire API 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.