# CMS NPI Registry Provider Search (`neuton/cms-npi-registry-provider-search`) Actor

Search the official CMS NPI Registry API for healthcare providers, organizations, taxonomies, addresses, identifiers, and contact fields.

- **URL**: https://apify.com/neuton/cms-npi-registry-provider-search.md
- **Developed by:** [Ashwin Prasad](https://apify.com/neuton) (community)
- **Categories:** Business, Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## CMS NPI Registry Provider Search

Search the official CMS NPI Registry API and export structured healthcare-provider records for provider enrichment, healthcare sales, payer/provider research, compliance checks, and data pipelines.

This actor is built for teams that need official NPI Registry rows without maintaining their own CMS API integration. It can enrich provider directories, healthcare sales lists, credentialing checks, payer/provider analytics, local market maps, and AI-agent/MCP workflows that need structured provider data.

### What it extracts

- NPI number, provider or organization name, status, and enumeration type
- Individual names, credentials, sex, enumeration date, and last-updated date
- Primary taxonomy, taxonomy code, license, and license state
- Location address, city, state, ZIP, phone, and fax
- Additional taxonomies, identifiers, source URL, and raw CMS payload

### Use cases

- Healthcare provider lead generation
- Provider directory enrichment
- Credentialing and onboarding data checks
- Local market mapping by city, state, and taxonomy
- Agent-callable healthcare data enrichment
- Build physician, clinic, organization, and taxonomy datasets for healthcare GTM or market research
- Join NPI rows into CRM, provider network, payer, compliance, or data-quality workflows

### Agent And Automation Use

The actor accepts city, state, taxonomy, name, organization, and exact NPI inputs. It returns structured rows with NPI, provider names, taxonomy, license state, address, phone, fax, identifiers, source URL, and raw CMS payload. Use it as a scheduled provider-enrichment job or an agent-callable healthcare lookup tool.

### SEO Keywords

NPI Registry scraper, CMS NPI API, NPI lookup API, healthcare provider scraper, provider directory enrichment, taxonomy code lookup, healthcare lead generation data, NPI provider search, physician database API.

### Input

Search by city, state, taxonomy description, individual name, organization name, or exact NPI.

### Pricing guidance

Recommended launch pricing: $3-$4 per 1,000 provider rows, increasing toward $5-$7 per 1,000 after repeat healthcare-data usage appears.

# Actor input Schema

## `city` (type: `string`):

Provider city filter.

## `state` (type: `string`):

Two-letter US state filter.

## `taxonomyDescription` (type: `string`):

Optional taxonomy description such as cardiology, dentist, or audiologist.

## `firstName` (type: `string`):

Optional individual provider first name.

## `lastName` (type: `string`):

Optional individual provider last name.

## `organizationName` (type: `string`):

Optional organization provider name.

## `npi` (type: `string`):

Optional exact NPI number.

## `maxResults` (type: `integer`):

Maximum provider rows to return.

## Actor input object example

```json
{
  "city": "Baltimore",
  "state": "MD",
  "taxonomyDescription": "",
  "firstName": "",
  "lastName": "",
  "organizationName": "",
  "npi": "",
  "maxResults": 100
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {};

// Run the Actor and wait for it to finish
const run = await client.actor("neuton/cms-npi-registry-provider-search").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {}

# Run the Actor and wait for it to finish
run = client.actor("neuton/cms-npi-registry-provider-search").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call neuton/cms-npi-registry-provider-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=neuton/cms-npi-registry-provider-search",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/cEDAg2bdNYrclY1vb/builds/XJsbahlZUS7gqDTGe/openapi.json