# NPI Lookup: NPI Registry Search for US Healthcare Providers (`wintersworks/npi-registry-provider-lookup`) Actor

NPI lookup for US healthcare providers and organizations in the official CMS NPPES NPI Registry, by NPI number, name or organization: specialty, license, practice address, status.

- **URL**: https://apify.com/wintersworks/npi-registry-provider-lookup.md
- **Developed by:** [Winters Works](https://apify.com/wintersworks) (community)
- **Categories:** Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.50 / 1,000 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.

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 Lookup: NPI Registry Search for US Healthcare Providers

Look up **US healthcare providers and organizations** in the official **CMS NPPES NPI Registry**. Give NPI numbers, provider names (`Last, First`) or organization names and get clean records: NPI, name, credential, primary specialty and taxonomy, license, practice location, phone, status and last-updated date. Export JSON, CSV or Excel.

### Use cases

- **Healthcare data teams:** validate and enrich NPI columns in claims, referral or credentialing files.
- **Billing and compliance:** confirm a provider's NPI is active and matches name and specialty.
- **Researchers:** pull specialty and location data for a list of organizations.
- **AI agents:** fast structured provider lookups via API or MCP.

### How it works

1. Each NPI number is looked up directly; names and organizations use the registry search.
2. The official NPPES NPI Registry API (v2.1) is queried; nothing is scraped.
3. Records are flattened into one row per provider or organization.
4. Name searches return up to `maxPerQuery` records per query; each record returned is one billed event.

### Input

```json
{
  "queries": [
    "1003000126",
    "Mayo Clinic"
  ],
  "state": "",
  "maxPerQuery": 3
}
```

Empty input `{}` runs a small demo. Other options: `state`, `maxPerQuery`, `maxResults`, `concurrency`.

### Output (one item per result)

```json
{
  "npi": "1003000126",
  "type": "individual",
  "name": "ARDALAN ENKESHAFI",
  "credential": "M.D.",
  "primarySpecialty": "Internal Medicine",
  "licenseNumber": "1957",
  "licenseState": "MD",
  "address": "6410 ROCKLEDGE DR STE 304",
  "city": "BETHESDA",
  "state": "MD",
  "postalCode": "208171841",
  "phone": "443-602-6207",
  "status": "active",
  "error": null
}
```

### Example output

Real output from a default run (some fields omitted for width):

| npi | type | name | status | primarySpecialty | city | state |
|---|---|---|---|---|---|---|
| 1003000126 | individual | ARDALAN ENKESHAFI | active | Hospitalist | BETHESDA | MD |
| 1881018208 | organization | MAYO CLINIC | active | Clinic/Center, Multi-Specialty | ROCHESTER | MN |

Every run also produces a ready-made table view in the Output tab, and you can export to JSON, CSV or Excel.

### Pricing

Pay per event: **$0.0015 per provider record** ($1.50 per 1,000). Duplicates, failed lookups and empty results are not charged.

### FAQ

**Is this legal?** The NPI Registry is public data that CMS publishes through its free public NPPES NPI Registry API, and this Actor queries that API directly with an identifying User-Agent and a short delay between requests (default 200 ms). Data is provided as-is and may be out of date; verify critical details with CMS or the NPPES registry itself. This Actor is not affiliated with or endorsed by CMS.

**Does it return patient data?** No. Only provider and organization registry entries, which are public by design.

**Is this for sending bulk outreach?** No. It is for lookup, validation and research. If you contact anyone you must follow CAN-SPAM, TCPA and other applicable laws.

**Are failures charged?** No. Errors and queries with no match are not charged.

### Limitations

Data is only as current as the NPPES registry; NPIs are US-only; name searches return at most 200 records per query.

### About

Built and maintained by Winters Works. Questions or feature requests: open an issue on the Actor page or email wintersworks.shop@gmail.com.

# Actor input Schema

## `queries` (type: `array`):

One per line: a 10-digit NPI number, an individual as 'Last, First', or an organization name (prefix match).

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

Two-letter US state code to narrow name searches, e.g. TX.

## `maxPerQuery` (type: `integer`):

Cap on records returned per name or organization query (each record is billed).

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

Cap on inputs processed (duplicates are skipped and never charged).

## `concurrency` (type: `integer`):

Parallel requests.

## Actor input object example

```json
{
  "queries": [
    "1003000126",
    "Mayo Clinic"
  ],
  "state": "",
  "maxPerQuery": 3,
  "maxResults": 1000,
  "concurrency": 3
}
```

# Actor output Schema

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

All result items from the run's default dataset.

# 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 = {
    "queries": [
        "1003000126",
        "Mayo Clinic"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("wintersworks/npi-registry-provider-lookup").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 = { "queries": [
        "1003000126",
        "Mayo Clinic",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("wintersworks/npi-registry-provider-lookup").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 '{
  "queries": [
    "1003000126",
    "Mayo Clinic"
  ]
}' |
apify call wintersworks/npi-registry-provider-lookup --silent --output-dataset

```

## MCP server setup

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

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/0D5FYnt0RybRkeyWc/builds/HchZdN3b3J8fzaImr/openapi.json