# NPI Provider Lookup & Enrichment (NPPES) (`sovereign_workspace/npi-provider-lookup`) Actor

Look up and enrich US healthcare providers via CMS NPPES — by NPI list or name/state/taxonomy prospecting; returns primary taxonomy code (codes only; NUCC descriptions not included).

- **URL**: https://apify.com/sovereign\_workspace/npi-provider-lookup.md
- **Developed by:** [Chase Mariano](https://apify.com/sovereign_workspace) (community)
- **Stats:** 2 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $5.00 / 1,000 provider records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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 Provider Lookup & Enrichment

Clean, normalized US provider records from the CMS **NPPES** registry.
Feed it a list of NPIs (enrichment mode) or a name/state/specialty
search (prospecting mode); get one dataset item per provider with
primary taxonomy code, practice address, phone and status — the columns a
credentialing check or a healthcare lead list actually needs, without
the registry's nested JSON.

**Pricing: pay per event.** `provider-record` — $0.005 per record.
Platform usage passed through. Zero matches costs nothing.

### Input

```json
{"last_name": "smith", "state": "CA", "taxonomy_description": "family medicine"}
```

### Example output

```json
{"npi": "1234567890", "type": "NPI-1", "name": "A Smith", "credential": "MD",
 "taxonomy_code": "207Q00000X",
 "address": "1 Main St", "city": "Fresno", "state": "CA", "zip": "93701",
 "phone": "555-0101", "status": "A", "last_updated": "2026-01-15"}
```

### Output fields

One dataset item per result; every field is always present
(empty or null when the source has no value). Defined in
`.actor/dataset_schema.json`.

| Field | Type | Description |
|---|---|---|
| `npi` | string | 10-digit National Provider Identifier |
| `type` | string | Enumeration type: NPI-1 (individual) or NPI-2 (organization) |
| `name` | string | Organization name, or first + last name for individuals |
| `credential` | string | Credential as registered (e.g. MD, DDS) |
| `status` | string | NPPES status (A = active) |
| `taxonomy_code` | string | Primary taxonomy code |

Taxonomy is output as the code only. Code descriptions come from the NUCC
Health Care Provider Taxonomy code set, which NUCC licenses for commercial
use, so this Actor doesn't output them. You can look codes up at
[nucc.org](https://www.nucc.org/).
| `address` | string | Practice location address line 1 |
| `city` | string | Practice location city |
| `state` | string | Practice location state |
| `zip` | string | Practice location 5-digit ZIP |
| `phone` | string | Practice location phone |
| `last_updated` | string | Date the NPPES record was last updated |

Runs stop cleanly at your max-charge limit: nothing is pushed past
what you agreed to pay for.

Source: CMS NPPES API v2.1 (public).

# Actor input Schema

## `profile` (type: `string`):

Named config preset applied at start. Any field you set explicitly below overrides the preset.

## `npis` (type: `array`):

Look up these specific 10-digit NPI numbers directly. When set, the search fields below are ignored.

## `last_name` (type: `string`):

Provider last name to search for (individual providers).

## `organization_name` (type: `string`):

Organization name to search for (facilities, practices).

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

Two-letter US state code to search within (e.g. CA, TX).

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

City to search within.

## `taxonomy_description` (type: `string`):

Provider specialty to search for, in plain words (e.g. dentist, cardiology).

## `limit` (type: `integer`):

Maximum number of provider records to return per run.

## Actor input object example

```json
{
  "limit": 100
}
```

# Actor output Schema

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

No description

## `errorCounters` (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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("sovereign_workspace/npi-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 = {}

# Run the Actor and wait for it to finish
run = client.actor("sovereign_workspace/npi-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 '{}' |
apify call sovereign_workspace/npi-provider-lookup --silent --output-dataset

```

## MCP server setup

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