# NPI Healthcare Provider Directory (specialty + location) (`hereditary_model/healthcare-provider-directory`) Actor

Builds healthcare provider lists by specialty and location from the public NPI registry: name, NPI, specialty, address, phone, and affiliations. Medtech sales and network research ready.

- **URL**: https://apify.com/hereditary\_model/healthcare-provider-directory.md
- **Developed by:** [Aaron Marxsen](https://apify.com/hereditary_model) (community)
- **Categories:** Lead generation, Business, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## NPI Registry Provider Lookup by Specialty and Location

Build a clean list of healthcare providers by specialty and location, straight from the public NPPES NPI registry. For each provider you get a normalized record: NPI number, name, credential, specialty, license, full practice address, and phone. Ready for medtech sales, provider network research, and referral mapping. Public registry data only: reliable, stable, and honest about what it contains.

Built for medtech sales teams, healthcare recruiters, and network researchers.

### Features

- Look up providers in the NPI registry by specialty and location
- Get NPI, name, credential, specialty, and license per provider
- Get full practice address and phone
- Forgiving specialty search that maps lay terms to NPI taxonomy
- Individual and organization records, normalized into one schema
- Pay per provider, no subscription

### Use cases

- Build a targeted list of providers for medtech outreach
- Map a provider network by specialty in a market
- Research referral sources for a practice
- Give a healthcare sales agent a provider lookup tool

### Input

| Field | Type | Description |
| --- | --- | --- |
| `specialty` | string (required) | Specialty or taxonomy keyword, for example Cardiology |
| `location` | string (required) | City and state, or just a state, for example Asheville, NC |
| `maxProviders` | integer (default 200) | Max records to return, up to 1200 |

```json
{ "specialty": "Cardiology", "location": "Asheville, NC", "maxProviders": 200 }
```

### Output

One record per provider:

```json
{
  "npi": 1234567890,
  "type": "individual",
  "name": "William Abernethy",
  "credential": "M.D.",
  "primarySpecialty": "Internal Medicine, Interventional Cardiology",
  "licenseState": "NC",
  "city": "ASHEVILLE",
  "state": "NC",
  "phone": "828-274-6000"
}
```

### Pricing: worked example

Pay per event. You are charged `search-init` at $0.05 once and `provider-extracted` at $0.01 per provider record.

Pulling 200 providers triggers 1 start ($0.05) and 200 provider events ($2.00). Total: $2.05.

### How to use

1. Open the actor and click Try for free.
2. Enter a specialty (for example Cardiology) and a location (city and state, or a state).
3. Set `maxProviders` to control list size and cost.
4. Click Start.
5. Download the provider list as CSV or JSON from the Storage tab.
6. Import into your CRM or network research tool.

### FAQ

**How do I search the NPI registry by specialty?**
Enter a specialty and a location. The actor maps common terms to NPI taxonomy (for example Cardiology to Cardiovascular Disease) and returns matching providers.

**Does it include email addresses?**
No. The NPI registry does not publish emails. Any tool that claims registry emails is inferring them elsewhere.

**Can I pull a whole state?**
Yes, up to 1200 records per query. Narrow by city for an exhaustive local pull.

**Is this data public?**
Yes. It comes from the public federal NPPES registry.

**Can an AI agent run this?**
Yes. It supports agentic payments, so a sales agent can build provider lists and pay per record.

### API and agents

Run it from the [Apify API](https://docs.apify.com/api/v2) or let an AI agent call it. Supports agentic payments via x402 and Skyfire (pay per event, limited permissions, no Standby).

```bash
curl -X POST "https://api.apify.com/v2/acts/hereditary_model~healthcare-provider-directory/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "specialty": "Cardiology", "location": "Asheville, NC" }'
```

### Related actors

- [Email and Social Media Extractor](https://apify.com/hereditary_model/contact-details-extractor)
- [ATS Job Postings Scraper](https://apify.com/hereditary_model/ats-job-postings-scraper)
- [Domain Intelligence API](https://apify.com/hereditary_model/domain-intelligence)
- [Local SEO Audit](https://apify.com/hereditary_model/local-seo-audit)
- [Website to Markdown for RAG and LLMs](https://apify.com/hereditary_model/website-to-markdown)
- [Broken Link Checker](https://apify.com/hereditary_model/broken-link-checker)
- [Bandcamp Discography Scraper](https://apify.com/hereditary_model/bandcamp-discography-scraper)

# Actor input Schema

## `specialty` (type: `string`):

Provider specialty or taxonomy keyword (matched against NPI taxonomy descriptions). Example: Cardiology, Physical Therapist, Pediatrics.

## `location` (type: `string`):

City and state, or just a state. Examples: Asheville, NC or NC. Used to filter providers by practice location.

## `maxProviders` (type: `integer`):

Maximum provider records to return. Each record is one billable event. The public registry returns up to 1200 per query.

## Actor input object example

```json
{
  "specialty": "Cardiology",
  "location": "Asheville, NC",
  "maxProviders": 200
}
```

# 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 = {
    "specialty": "Cardiology",
    "location": "Asheville, NC"
};

// Run the Actor and wait for it to finish
const run = await client.actor("hereditary_model/healthcare-provider-directory").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 = {
    "specialty": "Cardiology",
    "location": "Asheville, NC",
}

# Run the Actor and wait for it to finish
run = client.actor("hereditary_model/healthcare-provider-directory").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 '{
  "specialty": "Cardiology",
  "location": "Asheville, NC"
}' |
apify call hereditary_model/healthcare-provider-directory --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=hereditary_model/healthcare-provider-directory",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

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