# NPI Registry Lookup: US Healthcare Provider Data (NPPES) (`lepidata/npi-registry`) Actor

Search the CMS NPPES NPI Registry by NPI number, name, organization, specialty, city, state or ZIP: NPI, provider type, specialty and license, practice address and phone. Unofficial. Confirm at npiregistry.cms.hhs.gov.

- **URL**: https://apify.com/lepidata/npi-registry.md
- **Developed by:** [Lepi Data](https://apify.com/lepidata) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.20 / 1,000 npi provider records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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 Lookup: US Healthcare Provider Data

*Unofficial tool. Not affiliated with, endorsed by, or sponsored by the Centers for Medicare & Medicaid Services (CMS) or the U.S. Department of Health and Human Services.*

Search the NPPES NPI Registry and export US healthcare providers as one row per NPI. It's for healthcare staffing and credentialing teams, health-tech and billing companies, payers, pharma and device sales operations, and researchers.

**Input:** NPI numbers, or a search by specialty, provider or organization name, city, state and ZIP code.

**Output:** NPI, provider type, name and credential (or organization name), status, enumeration and last-updated dates, primary specialty with license state and number, all specialties, primary practice address, phone and fax, other practice locations and a link to the registry page.

**Confirm at npiregistry.cms.hhs.gov** before relying on any record. Registry data is self-reported by providers and can change.

### NPI lookup input

- `npiNumbers`: 10-digit NPIs, up to 1,000 (check digit validated)
- `taxonomyDescription`: specialty in NPPES taxonomy wording, e.g. Family Medicine, Internal Medicine, Dentist, Pharmacy
- `firstName`, `lastName`, `organizationName`: a trailing `*` matches a prefix
- `city`, `state`, `postalCode`
- `enumerationType`: `any` (default), `individual` or `organization`
- `maxResults`: up to 10,000

State or provider type alone is too broad for the NPI API: add a specialty, name, city or ZIP. The API returns at most 1,200 providers per search, so narrow by city or ZIP for larger pulls.

### Output fields

`npi`, `enumerationType`, `organizationName`, `firstName`, `middleName`, `lastName`, `namePrefix`, `nameSuffix`, `credential`, `status`, `enumerationDate`, `lastUpdated`, `primaryTaxonomyCode`, `primaryTaxonomy`, `primaryTaxonomyState`, `primaryTaxonomyLicense`, `taxonomies`, `practiceAddress`, `practicePhone`, `practiceFax`, `otherPracticeLocations`, `registryUrl`, `confirmAt`

Provider and practice fields only. Mailing addresses, Direct messaging addresses, authorized-official contacts, gender and other identifiers are left out.

Free status rows (not charged): `no-results`, `invalid-input`, `api-error`, `free-plan-limit`, `charge-limit-reached`.

**Example:** `{"taxonomyDescription":"Family Medicine","city":"Austin","state":"TX","maxResults":20}`

### Data source and compliance

- Source: the official CMS NPPES NPI Registry API, version 2.1 (npiregistry.cms.hhs.gov/api). Public, no key. Paced at about 2 requests a second.
- Not medical advice, and not a credentialing or licensing verification. Confirm at npiregistry.cms.hhs.gov.
- No CMS or HHS logos are used.
- Free-plan accounts get up to 100 results per run.

**Pricing.** Pay per result: $0.20 per 1,000 providers ($0.0002 each), the same price on every plan, no start fee. Free status rows are never charged.

# Actor input Schema

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

Optional 10-digit NPI numbers to look up, up to 1,000. Each is checked for a valid check digit.

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

Specialty (taxonomy) text, e.g. Family Medicine, Internal Medicine, Dentist, Pharmacy. Matched against the NPPES taxonomy text, so use the taxonomy wording ("Cardiovascular Disease", not "Cardiology").

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

Individual provider first name. A trailing \* matches a prefix (at least 2 letters).

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

Individual provider last name. A trailing \* matches a prefix.

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

Organization (group, hospital, pharmacy) name. A trailing \* matches a prefix.

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

Practice city.

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

2-letter state code. State alone is too broad: add a specialty, name, city or ZIP.

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

5 or 9 digits.

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

Individuals, organizations or both.

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

Up to 10,000. The NPI API returns at most 1,200 providers per search: narrow by city or ZIP for more.

## Actor input object example

```json
{
  "taxonomyDescription": "Family Medicine",
  "city": "Austin",
  "state": "TX",
  "enumerationType": "any",
  "maxResults": 20
}
```

# Actor output Schema

## `items` (type: `string`):

All rows from this run.

# 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": "Family Medicine",
    "city": "Austin",
    "state": "TX",
    "maxResults": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("lepidata/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 = {
    "taxonomyDescription": "Family Medicine",
    "city": "Austin",
    "state": "TX",
    "maxResults": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("lepidata/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 '{
  "taxonomyDescription": "Family Medicine",
  "city": "Austin",
  "state": "TX",
  "maxResults": 20
}' |
apify call lepidata/npi-registry --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,lepidata/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/wXqUMupYR1A65NQkJ/builds/oWzK5iGKhvMD9TxEb/openapi.json