# NPI Registry Search – US Doctors & Healthcare Providers (`gazidev/npi-registry-search`) Actor

Search the official CMS NPPES NPI Registry: doctors, dentists, therapists, clinics and pharmacies by specialty, state, city or ZIP, or look up NPIs in bulk. Practice address, phone, fax, taxonomy, license, authorized official. Beats the 1,200-result API cap. $1 per 1,000 providers.

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

## Pricing

from $1.00 / 1,000 providers

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## NPI Registry Search – US Doctors, Dentists & Healthcare Providers (NPPES)

Search and export **US healthcare providers from the official CMS NPPES NPI Registry**: doctors, dentists, nurse practitioners, therapists, chiropractors, pharmacies, clinics and hospitals. Filter by **specialty (taxonomy), state, city or ZIP code**, by name, or **look up thousands of NPI numbers in bulk**. One clean row per provider, with practice address, phone, fax, primary specialty, license number, authorized official and Direct messaging address.

- **Official public API only.** It uses the CMS NPPES NPI Registry API (`npiregistry.cms.hhs.gov`). No login, no API key, no browser.
- **Gets past the 1,200-result limit.** The NPI API returns at most 1,200 results per query. When a search hits that cap, the Actor automatically splits it by ZIP-code prefix (and individuals vs organizations) so you can export a whole state.
- **$1 per 1,000 providers.** Invalid and not-found NPIs are free. Start fee $0.00005.

### What can I use it for?

- **Healthcare lead lists:** every dentist, chiropractor or physical therapist in a city, ZIP area or state, with practice phone and address.
- **NPI verification in bulk:** check that the NPIs in your claims, CRM or credentialing file exist, and get each provider's current specialty, license and address.
- **Market research:** count providers by specialty and area; find new practices by enumeration date.
- **Data enrichment:** add taxonomy codes, license numbers and authorized officials to your own provider list.

### Input

Prefilled example (Dentists in Austin, TX, first 100):

```json
{
  "taxonomies": ["Dentist"],
  "states": ["TX"],
  "cities": ["Austin"],
  "maxResults": 100
}
```

| Field | What it does |
|---|---|
| `taxonomies` | Specialties as NPPES writes them: Dentist, Family Medicine, Chiropractor, Physical Therapist, Nurse Practitioner, Pharmacy, Clinical Social Worker... |
| `states`, `cities`, `postalCodes` | Where to search. Every specialty is searched in every location. ZIP prefixes such as `787*` are allowed. |
| `providerType` | Individuals (NPI-1), organizations (NPI-2) or both |
| `primaryTaxonomyOnly` | Keep only providers whose *primary* specialty matches (the registry also matches secondary ones) |
| `firstName`, `lastName`, `organizationName` | Name search; a trailing `*` wildcard works after 2 letters |
| `npiNumbers`, `bulkNpis` | Bulk NPI lookup; paste a column from a spreadsheet |
| `maxResults` | Stop after this many providers (0 = no limit) |
| `autoSplit` | Split capped searches by ZIP prefix to get past 1,200 results (on by default) |

**Note:** the registry needs at least one criterion besides a state (a specialty, city, ZIP or name). City and state match any of the provider's addresses (practice or mailing).

### Output

One row per provider. The **Providers** and **Contact details** tables in the Output tab show the main columns; JSON/CSV/Excel exports contain everything.

```json
{
  "npi": "1881105682",
  "providerType": "Individual",
  "name": "Dr. SARAH KHALID ABDAT",
  "credential": "B.D.S, M.S",
  "primaryTaxonomyCode": "1223E0200X",
  "primaryTaxonomy": "Dentist, Endodontics",
  "primaryLicense": "33568",
  "primaryLicenseState": "TX",
  "practiceStreet": "4400-1 E CENTRAL TEXAS EXPY STE B",
  "practiceCity": "KILLEEN",
  "practiceState": "TX",
  "practiceZip": "76543-7309",
  "practicePhone": "254-699-7855",
  "mailingCity": "AUSTIN",
  "otherPracticeLocations": [{"street": "3801 BEE CAVES RD STE C", "city": "WEST LAKE HILLS", "state": "TX", "phone": "512-328-6763"}],
  "enumerationDate": "2017-10-19",
  "lastUpdated": "2018-03-17",
  "status": "Active",
  "npiRegistryUrl": "https://npiregistry.cms.hhs.gov/provider-view/1881105682"
}
```

Organizations also get `organizationName`, `otherOrganizationNames`, `authorizedOfficial`, `authorizedOfficialTitle` and `authorizedOfficialPhone`. Every row has all `taxonomies` (code, description, license, state), `otherIdentifiers`, `endpoints` and `directAddress` (Direct secure messaging address, when the provider published one). A `SUMMARY` record in the key-value store lists API calls, duplicates and capped searches.

### Pricing

Pay per event: **$0.001 per provider saved** ($1 per 1,000) + $0.00005 per run. Invalid NPIs, not-found NPIs, duplicates and rows filtered by `primaryTaxonomyOnly` are not charged. The Actor stops cleanly when your maximum total charge is reached.

| Actor (Apify Store, Oct 2026) | Price per 1,000 providers |
|---|---|
| **NPI Registry Search (this Actor)** | **$1** |
| pink_comic/nppes-npi-registry | $2 (+ $0.0001 start) |
| sourabhbgp/npi-registry-scraper | $2 |
| neuton/cms-npi-registry-provider-search | $3 |

Example: all individual dentists in Texas (~20,000 rows) cost about $20 and take a few minutes at the default polite rate.

### FAQ

**Is this data public?** Yes. CMS publishes NPPES data under the HIPAA Administrative Simplification rules; the NPI Registry is a free public lookup. The Actor only reads the official public API.

**Why do I see providers outside my city?** The registry matches the city against any address on file, including mailing addresses. Filter on `practiceCity` afterwards if you need practice location only.

**Does it include emails?** NPPES has no email field. Some providers publish a Direct secure messaging address, which is returned as `directAddress`.

**How fresh is the data?** The API is CMS's live registry; `lastUpdated` shows when the provider last changed their record.

**Can I use it for marketing?** The data is public, but your outreach must follow the laws that apply to you (for example TCPA rules for calls and texts, and CAN-SPAM for email).

### Use with AI agents / Apify MCP

Add this Actor as a tool in the Apify MCP server (`mcp.apify.com`) and ask your agent things like *"find pediatric dentists in ZIP 787* with their phone numbers"\* or *"verify these 50 NPIs"*. The flat JSON rows are easy for an LLM to read.

### Related Actors

- [US Business Entity Leads](https://apify.com/gazidev/us-business-entity-leads) – new US company filings.
- [Website Contact Finder](https://apify.com/gazidev/website-contact-finder) – emails and social links from websites.

# Actor input Schema

## `taxonomies` (type: `array`):

Provider taxonomy descriptions as used by NPPES, e.g. Dentist, Family Medicine, Chiropractor, Physical Therapist, Nurse Practitioner, Pharmacy, Clinical Social Worker. Partial words work ("Dent" is not enough; use whole words). Each specialty is searched in every location below.

## `states` (type: `array`):

2-letter US state codes (TX, CA, NY...). The registry needs one more criterion with a state: a specialty, city, ZIP or name.

## `cities` (type: `array`):

Optional. Combined with every state above (Austin + TX).

## `postalCodes` (type: `array`):

Optional. 5-digit ZIP codes or a prefix with a trailing \* (at least 2 digits), e.g. 787\* for the Austin area.

## `providerType` (type: `string`):

Individuals (NPI-1: doctors, dentists, therapists), organizations (NPI-2: clinics, hospitals, pharmacies) or both.

## `primaryTaxonomyOnly` (type: `boolean`):

The registry also matches secondary taxonomies. Turn on to keep only providers whose primary taxonomy contains your specialty text (filtered rows are not charged).

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

Individual's first name. Trailing \* wildcard allowed after 2 letters (Jo\*).

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

Individual's last name. Trailing \* wildcard allowed after 2 letters.

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

Organization (NPI-2) name, e.g. "Kaiser\*" or "Smile Dental".

## `npiNumbers` (type: `array`):

10-digit NPIs to look up. Invalid numbers (bad check digit) and not-found NPIs are reported free of charge.

## `bulkNpis` (type: `string`):

Paste NPIs separated by new lines, commas or spaces (e.g. a column from a spreadsheet).

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

Stop after this many providers. 0 = no limit.

## `autoSplit` (type: `boolean`):

The NPI API returns at most 1,200 results per query. When a search hits that cap, the Actor automatically splits it into ZIP-code prefixes (and individuals vs organizations) to reach the rest.

## `requestsPerSecond` (type: `integer`):

Polite request rate to the public CMS API.

## Actor input object example

```json
{
  "taxonomies": [
    "Dentist"
  ],
  "states": [
    "TX"
  ],
  "cities": [
    "Austin"
  ],
  "providerType": "any",
  "primaryTaxonomyOnly": false,
  "maxResults": 100,
  "autoSplit": true,
  "requestsPerSecond": 3
}
```

# Actor output Schema

## `providers` (type: `string`):

No description

## `contacts` (type: `string`):

No description

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

No description

## `summary` (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 = {
    "taxonomies": [
        "Dentist"
    ],
    "states": [
        "TX"
    ],
    "cities": [
        "Austin"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("gazidev/npi-registry-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 = {
    "taxonomies": ["Dentist"],
    "states": ["TX"],
    "cities": ["Austin"],
}

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

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

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

```

## CLI example

```bash
echo '{
  "taxonomies": [
    "Dentist"
  ],
  "states": [
    "TX"
  ],
  "cities": [
    "Austin"
  ]
}' |
apify call gazidev/npi-registry-search --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,gazidev/npi-registry-search"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/NE7cy6hslkWwofQy9/builds/LMche43BRTTP3YnPd/openapi.json