# NPI Registry: Healthcare Provider Search (`cheerful_term/npi-registry`) Actor

Search the CMS NPPES NPI Registry for doctors, clinics, pharmacies, therapists and every other US healthcare provider: NPI, name, credential, primary taxonomy, license state, practice address and phone, authorized official, enumeration date.

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

## Pricing

$2.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: Healthcare Provider Search

Search the CMS NPPES NPI Registry for doctors, clinics, pharmacies, therapists and every other US healthcare provider: NPI, name, credential, primary taxonomy, license state, practice address and phone, authorized official, enumeration date.

### Why use it

The federal registry every billing provider must be in, searched live. Phone numbers are the practice location numbers providers publish in NPPES.

### Who it's for

- Healthcare sales and recruiting teams building provider lists by specialty and city
- Payers and credentialing teams verifying an NPI
- Researchers mapping provider supply

### Input

| Field | What it does |
|---|---|
| `taxonomy` | **Specialty / taxonomy**. e.g. Physical Therapist, Dentist, Pharmacy |
| `city` | **City**. e.g. Minneapolis |
| `state` | **State**. Two-letter code |
| `zip` | **ZIP code**. 5-digit ZIP |
| `providerType` | **Provider type**. NPI-1 individuals, NPI-2 organizations. |
| `organizationName` | **Organization name**. Organization name (wildcard \* allowed) |
| `lastName` | **Last name**. Individual's last name |
| `firstName` | **First name**. Individual's first name |
| `npi` | **NPI number**. Look up one NPI |
| `maxItems` | **Max results**. Stop after this many results. Each result is one billed event. |

Example input:

```json
{
  "taxonomy": "Physical Therapist",
  "city": "Minneapolis",
  "state": "MN",
  "maxItems": 100
}
```

### Output

One dataset item per result. A real item from a test run:

```json
{
  "npi": "1538287404",
  "type": "Organization",
  "name": "ABBOTT NORTHWESTERN HOSPITAL",
  "status": "A",
  "enumerationDate": "2007-03-27",
  "lastUpdated": "2008-06-13",
  "authorizedOfficial": "JANE NEWMAN",
  "authorizedOfficialTitle": "Physical Therapist",
  "primaryTaxonomy": "Physical Therapist",
  "taxonomyCode": "225100000X",
  "licenseState": "MN",
  "address": "800 E 28TH ST",
  "city": "MINNEAPOLIS",
  "state": "MN",
  "zip": "55407",
  "phone": "612-863-4447"
}
```

Download as JSON, CSV, Excel or via the Apify API.

### Pricing

Pay per result: **$0.002 per provider** ($2 per 1,000). No monthly fee. Set a max charge on the run and it stops there. AI agents can run it with agentic payments where Apify enables them.

### Data source

Fetched live at run time from the public source: https://npiregistry.cms.hhs.gov/api/

Public records only. Nothing is fetched behind a login.

### Limits

- The NPPES API returns at most 1,200 results per search; split by city or ZIP for more.

### Use it from code or an AI agent

```bash
curl -X POST 'https://api.apify.com/v2/acts/cheerful_term~npi-registry/run-sync-get-dataset-items?token=YOUR_TOKEN' \
  -H 'Content-Type: application/json' -d '{"taxonomy": "Physical Therapist", "city": "Minneapolis", "state": "MN", "maxItems": 100}'
```

Part of a set of public-records actors by cheerful_term: https://apify.com/cheerful_term

# Actor input Schema

## `taxonomy` (type: `string`):

e.g. Physical Therapist, Dentist, Pharmacy

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

e.g. Minneapolis

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

Two-letter code

## `zip` (type: `string`):

5-digit ZIP

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

NPI-1 individuals, NPI-2 organizations.

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

Organization name (wildcard \* allowed)

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

Individual's last name

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

Individual's first name

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

Look up one NPI

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

Stop after this many results. Each result is billed as one event.

## Actor input object example

```json
{
  "taxonomy": "Physical Therapist",
  "city": "Minneapolis",
  "state": "MN",
  "maxItems": 100
}
```

# Actor output Schema

## `overview` (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 = {
    "taxonomy": "Physical Therapist",
    "city": "Minneapolis",
    "state": "MN",
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("cheerful_term/npi-registry").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 = {
    "taxonomy": "Physical Therapist",
    "city": "Minneapolis",
    "state": "MN",
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("cheerful_term/npi-registry").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 '{
  "taxonomy": "Physical Therapist",
  "city": "Minneapolis",
  "state": "MN",
  "maxItems": 100
}' |
apify call cheerful_term/npi-registry --silent --output-dataset

```

## MCP server setup

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

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/EH3xYa5KeqQzMH8OX/builds/ZbbZMitZuIxmGDKRd/openapi.json