NPPES vs RecipeAPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useyesunclear
Data licenseU.S. Government (public NPI data)Unverified
Free tierFree — no key requiredFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

NPPES vs RecipeAPI: common questions

Which is more reliable, NPPES or RecipeAPI?

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

NPPES needs no key, while RecipeAPI requires a free API key. If you want to start calling without signup, reach for NPPES first.

Can I call NPPES and RecipeAPI from the browser?

Only RecipeAPI 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 RecipeAPI free for commercial use?

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