NPI lookup and enrichment
Normalize public NPPES records by NPI, entity type, name, taxonomy, address, enumeration date, last-updated date, and status.
Market catalog
A proposed API and CSV feed product for teams that need public CMS NPPES NPI Registry records normalized by NPI, entity type, provider or organization name, taxonomy, geography, enumeration date, last-updated date, status, and source reference.
{
"data": [
{
"npi": "3456789012",
"entityType": "NPI-2",
"organizationName": "Demo Medical Supplies Inc",
"taxonomyCode": "332B00000X",
"taxonomyDescription": "Durable Medical Equipment & Medical Supplies",
"city": "Washington",
"state": "DC",
"postalCode": "20037",
"enumerationDate": "2026-01-19",
"lastUpdated": "2026-01-19",
"status": "A",
"source": "NPPES API-compatible sample"
}
],
"meta": { "sampleOnly": true, "market": "provider-directory" }
}
This catalog entry summarizes the buyer fit, sources, and access model for this data product.
The initial product would normalize public records into stable polling endpoints and exports.
These are the specific self-serve workflows this page is designed to support.
Normalize public NPPES records by NPI, entity type, name, taxonomy, address, enumeration date, last-updated date, and status.
Route provider taxonomy and location changes into healthcare CRM, provider network, medtech sales, and RCM data workflows.
Refresh CSV snapshots and API cache when public NPPES records or downloadable registry files are updated.
These pages focus on specific buyer workflows.
Pricing starts with narrow, low-touch access paths for qualified buyers.
No. This is a product page for reviewing the proposed response shape, source coverage, and buyer fit.
No. The proposed product would normalize public NPPES provider identifier records and source links only. Buyers remain responsible for credentialing, network, billing, legal, quality, and provider-data decisions.