# US NPI Registry — Healthcare Provider Scraper (`straightforward_hydra/us-npi-registry-scraper`) Actor

Search the official CMS NPPES registry of US healthcare providers by specialty, state or name: NPI, specialty, license, practice address & phone. No key.

- **URL**: https://apify.com/straightforward\_hydra/us-npi-registry-scraper.md
- **Developed by:** [Dev D](https://apify.com/straightforward_hydra) (community)
- **Categories:** Developer tools, Automation, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.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/platform/actors/running/actors-in-store#pay-per-event

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

## US NPI Registry — Healthcare Provider Scraper 🩺

**Search the official CMS NPPES registry of every US healthcare provider — by specialty, state, city or name — and get clean rows: NPI, name, specialty/taxonomy, license, practice address, phone and fax. No API key.**

The **NPPES NPI Registry** is the U.S. government's authoritative directory of all HIPAA-covered healthcare providers — ~8 million individuals (doctors, dentists, nurses, therapists…) and organizations (hospitals, pharmacies, labs, clinics…), each with a unique **National Provider Identifier (NPI)**. This Actor turns it into structured, ready-to-use rows.

Unlike map-based business scrapers, this is the **licensed-provider registry itself** — every record has an NPI, specialty taxonomy and (for many) a state license number.

***

### What you get per provider

`npi` · `type` (Individual / Organization) · `name` · `first_name` / `last_name` / `credential` · `organization_name` · `primary_specialty` · `taxonomy_code` · `license_number` · `license_state` · `specialties[]` · `address` · `city` · `state` · `postal_code` · `phone` · `fax` · `status` · `enumeration_date` · `last_updated` · `source_url`.

### Examples

**Every dentist in California**

```json
{ "taxonomyDescription": "dentist", "state": "CA" }
```

**Pharmacies in one city**

```json
{ "taxonomyDescription": "pharmacy", "state": "TX", "city": "Houston", "enumerationType": "NPI-2" }
```

**Look up a single NPI**

```json
{ "npiNumber": "1760813802" }
```

**Find a provider by name**

```json
{ "lastName": "smith", "firstName": "jo*", "state": "NY" }
```

### Use cases

- **Healthcare lead generation & marketing** — targeted B2B lists by specialty and geography.
- **Credentialing & provider-data management** — verify NPI, license and taxonomy.
- **Claims / RCM & directory apps** — enrich or build provider directories.
- **Research & analytics** — provider supply by specialty and region.

### Notes

- **No API key.** Uses the keyless official CMS NPPES API (v2.1).
- **Wildcards:** name and organization fields accept a trailing `*` (e.g. `kaiser*`).
- **State needs a partner field.** The API won't search on `state` alone — combine it with a specialty, city, name or ZIP.
- **~1,200 records per query.** The public API caps results at 200/page and 1,000 skipped, so a single query returns at most ~1,200 providers. For large states, split by **city** or **ZIP** to page through everything.
- Data is public U.S. government information (NPPES), free to use.

***

#### Keywords

NPI, NPPES, NPI registry, healthcare providers, physicians, doctors, dentists, pharmacies, hospitals, provider directory, taxonomy, specialty, medical license, credentialing, healthcare leads, CMS, HIPAA, provider data, no API key.

# Actor input Schema

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

Provider specialty, e.g. "dentist", "pharmacy", "internal medicine", "chiropractor". Partial matches allowed.

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

2-letter US state code, e.g. "CA", "NY", "TX". NPPES requires state to be combined with at least one other field (e.g. specialty or city).

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

Practice city, e.g. "San Francisco". Useful to page past the ~1,200-record cap on big states.

## `postalCode` (type: `string`):

5-digit ZIP or ZIP prefix, e.g. "9410".

## `enumerationType` (type: `string`):

Individuals (NPI-1) or organizations (NPI-2). Leave as Any for both.

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

Individual provider first name. Wildcards allowed, e.g. "jo\*".

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

Individual provider last name. Wildcards allowed, e.g. "smi\*".

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

Organization / facility name. Wildcards allowed, e.g. "kaiser\*".

## `npiNumber` (type: `string`):

Exact 10-digit NPI to look up a single provider.

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

Cap on rows returned. NPPES returns at most ~1,200 per query; refine by city/ZIP for more.

## Actor input object example

```json
{
  "taxonomyDescription": "dentist",
  "state": "CA",
  "enumerationType": "",
  "maxResults": 1000
}
```

# 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 = {
    "taxonomyDescription": "dentist",
    "state": "CA"
};

// Run the Actor and wait for it to finish
const run = await client.actor("straightforward_hydra/us-npi-registry-scraper").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 = {
    "taxonomyDescription": "dentist",
    "state": "CA",
}

# Run the Actor and wait for it to finish
run = client.actor("straightforward_hydra/us-npi-registry-scraper").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 '{
  "taxonomyDescription": "dentist",
  "state": "CA"
}' |
apify call straightforward_hydra/us-npi-registry-scraper --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

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