# NPI Registry Scraper: US Doctors, Dentists & Clinics (`tacps126/npi-providers`) Actor

US healthcare providers from the official NPI Registry: doctors, dentists, therapists, clinics and hospitals with specialty, license, practice address, phone, fax and the authorized official of organizations. Search by specialty, state, city, ZIP, name or NPI; new-provider alerts.

- **URL**: https://apify.com/tacps126/npi-providers.md
- **Developed by:** [Tapaswai Choudhary](https://apify.com/tacps126) (community)
- **Categories:** Lead generation, Automation
- **Security:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.40 / 1,000 providers

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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 Scraper — US Doctors, Dentists & Clinics

US healthcare providers from the official **NPI Registry** (CMS NPPES): doctors, dentists, nurse practitioners, therapists, pharmacists, clinics, practices and hospitals. Each provider comes with **specialty, license number and state, practice address, phone and fax**, mailing address, and for organizations the **authorized official** (name, title, phone). Search by specialty, state, city, ZIP code, name or NPI; get **new practices** as they register.

**Built for** healthcare B2B sales (dental and medical supplies, software, pharma), medical staffing and recruiting, healthcare marketing agencies, insurers and provider networks, and AI agents.

### What you get

| Field | Meaning |
|---|---|
| `npi`, `type`, `name`, `credential`, `gender`, `status`, `enumerationDate`, `lastUpdated` | The provider |
| `specialty`, `taxonomyCode`, `licenseNumber`, `licenseState`, `taxonomies` | What they practise and where they're licensed |
| `street`, `city`, `state`, `zip`, `phone`, `fax`, `mailingAddress` | Where to reach them |
| `authorizedOfficial` (name, title, credential, phone) | Who signs for an organization |
| `otherNames`, `directAddresses`, `url` | Doing-business-as names, Direct messaging addresses, registry page |

### Why this Actor

- **Official source**, every US provider with an NPI (about 9 million records).
- **Complete lists:** combine specialties with states and cities or ZIP codes; the Actor runs every combination.
- **New practices:** *New in the last N days* + *Only new providers* on a schedule.
- **For AI agents.** Callable as an MCP tool.

### How to use it

Dental practices in Austin and Dallas:

```json
{ "specialties": ["Dentist"], "states": ["TX"], "cities": ["Austin", "Dallas"], "providerType": "organization" }
```

New chiropractors in Florida each week:

```json
{ "specialties": ["Chiropractor"], "states": ["FL"], "cities": ["Miami", "Orlando", "Tampa"], "enumeratedWithinDays": 30, "onlyNew": true }
```

### Pricing

**$3 per 1,000 providers** plus a small start fee per run. On the Apify free plan a run returns up to 100 providers.

### Good to know

- The registry answers about 1,200 results per search: add cities or ZIP codes to get everyone in a big state (the run says when a search hit the limit).
- Data is as providers report it to CMS. Questions: **tacps126@gmail.com**.

# Actor input Schema

## `specialties` (type: `array`):

Registry specialty names, e.g. Dentist, Family Medicine, Chiropractor, Physical Therapist, Pharmacist, Nurse Practitioner.

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

Two-letter codes, e.g. TX, CA.

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

Practice cities. Splitting a state into cities gets past the registry's ~1,200 results per search.

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

Five-digit ZIP codes (instead of states and cities).

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

Individuals or organizations.

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

Individuals.

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

Individuals.

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

Organizations (use \* for a prefix, e.g. smile\*).

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

Look up these NPIs.

## `enumeratedWithinDays` (type: `integer`):

Only providers whose NPI was issued in this window (new practices and new graduates).

## `withPhoneOnly` (type: `boolean`):

Only providers with a practice phone number.

## `maxItems` (type: `integer`):

Most providers returned per run.

## `onlyNew` (type: `boolean`):

Schedule the Actor and each run returns only providers earlier runs did not deliver.

## `monitorName` (type: `string`):

Optional name for the “only new” history, so several monitors can run side by side.

## `tenantId` (type: `string`):

Optional label used to keep separate histories for different clients or teams.

## `debug` (type: `boolean`):

Save extra diagnostics with the run (for support requests).

## Actor input object example

```json
{
  "specialties": [
    "Dentist"
  ],
  "states": [
    "TX"
  ],
  "cities": [
    "Austin"
  ],
  "providerType": "any",
  "withPhoneOnly": false,
  "maxItems": 1000,
  "onlyNew": false,
  "debug": false
}
```

# Actor output Schema

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

The produced items (default dataset items).

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

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

# Run the Actor and wait for it to finish
run = client.actor("tacps126/npi-providers").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 '{
  "specialties": [
    "Dentist"
  ],
  "states": [
    "TX"
  ],
  "cities": [
    "Austin"
  ]
}' |
apify call tacps126/npi-providers --silent --output-dataset

```

## MCP server setup

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

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/COsT6KbR22irsaWbe/builds/drX9d4hUlIkdzAlJR/openapi.json
