NPPES vs Open Brewery DB

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms910614
P95 · ms20712735
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseU.S. Government (public NPI data)Unverified (open dataset)
Free tierFree — no key requiredFree — no key
Rate limitUnpublished120 req/window · 114 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

NPPES vs Open Brewery DB: common questions

Which is more reliable, NPPES or Open Brewery DB?

Both are neck-and-neck — NPPES and Open Brewery DB 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, NPPES or Open Brewery DB?

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

Neither needs a paid key — NPPES is callable with no signup, and Open Brewery DB is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call NPPES and Open Brewery DB from the browser?

Only Open Brewery DB 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 NPPES and Open Brewery DB free for commercial use?

NPPES allows commercial use on its free tier, and Open Brewery DB 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.