NPI Registry Provider Lookup & Enrichment

Search and export US healthcare providers — doctors, nurses, pharmacies, clinics, hospitals — straight from the official NPI Registry (CMS, public data). Clean, normalized, de-noised output you can drop into a CRM or sales workflow.

Why this Actor

The NPI Registry's public API has a well-known quirk: broad searches on common names (e.g. Smith) silently return alphabetical noise instead of real matches. This Actor fixes that: it over-fetches and verifies every record actually matches your query before returning it — so you get only real Smiths, not a random page of providers.

Input

{ "lastName": "Smith", "state": "CA", "taxonomy": "Family Medicine", "maxItems": 100 }

{ "npiNumbers": ["1932195542", "1184750002"] }

{ "organizationName": "CVS Pharmacy", "providerType": "organization", "state": "TX", "maxItems": 50 }

Field	Description
npiNumbers[]	Exact 10-digit NPI lookups. If set, search filters are ignored.
lastName / firstName	Individual provider name (verified against results).
organizationName	Organization / practice name (verified against results).
taxonomy	Specialty, e.g. "Pharmacy", "Family Medicine", "Internal Medicine".
city / state / postalCode	Location filters. State is strongly recommended to narrow common names.
providerType	any / individual (NPI-1) / organization (NPI-2).
maxItems	Max matching providers to return (controls cost).
enrichContacts	Best-effort: probe a website (from registry endpoints) for a contact email.

Output

{
  "npi": "1932195542",
  "enumerationType": "NPI-1",
  "providerName": "BRENNA ELAINE BAYNARD-SMITH",
  "credential": "MD",
  "organizationName": null,
  "primaryTaxonomy": "Family Medicine",
  "primaryTaxonomyCode": "207Q00000X",
  "taxonomies": ["Family Medicine"],
  "addressLine1": "555 S 7TH AVE",
  "city": "BARSTOW", "state": "CA", "postalCode": "923111303", "country": "US",
  "phone": "760-255-2400", "fax": "760-255-2401",
  "authorizedOfficial": null,
  "endpoints": [],
  "website": null,
  "email": null,
  "npiUrl": "https://npiregistry.cms.hhs.gov/provider-view/1932195542"
}

Organizations (NPI-2) additionally populate organizationName, authorizedOfficial, and authorizedOfficialPhone.

Reliability notes

• Precision-first: every returned record is verified to match your name/org/taxonomy.
• The NPI API caps retrieval at 1,200 records per query. For very common names, add state, city, or taxonomy to surface more matches — the Actor logs a clear warning when it hits this cap.
• Exponential backoff on rate limits / server errors; one failed lookup never sinks the run.
• email/website are best-effort — the NPI Registry rarely lists practice websites, so these are frequently empty. The Actor's core value is the registry data itself (provider, specialty, address, phone, organization, authorized official).

Pricing

Pay per result. Built for high-volume, low-cost enrichment.

Data usage & compliance

All data comes from the public NPI Registry operated by CMS (Centers for Medicare & Medicaid Services), which is published in the public domain for transparency. This Actor performs only lookups against the official public API. Use the data in accordance with applicable laws (e.g. HIPAA does not cover NPI directory data, but downstream use may carry obligations); do not use it for spam or harassment.

How to use NPI Registry Provider Lookup & Enrichment

1. Open NPI Registry Provider Lookup & Enrichment on Apify Store and click Try for free.
2. Fill in the input (the form is prefilled with a working example) and click Start.
3. Watch results appear in the Output tab, then download them as JSON, CSV, Excel or HTML, or read them through the API.
4. Optional: save the input as a task and add a schedule to run it automatically, or connect it to your tools with integrations and webhooks.

Use NPI Registry Provider Lookup & Enrichment with AI agents (MCP)

Give Claude, ChatGPT, Cursor, VS Code or any MCP client this Actor as a tool through the hosted Apify MCP server. The agent sees the input fields with descriptions and example values, runs the Actor, and reads the results.

MCP server URL (this Actor only):

https://mcp.apify.com/?tools=technicaldost/npi-registry-enrichment

Claude Code:

$claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/npi-registry-enrichment" --header "Authorization: Bearer YOUR_APIFY_TOKEN"

Cursor, VS Code, Claude Desktop and other clients (mcp.json or the client's MCP settings):

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=technicaldost/npi-registry-enrichment",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}

Clients that support sign-in (such as Claude.ai connectors) can use the URL without a token and log in to Apify instead. Get your token in Apify Console → Settings → API & Integrations, or generate a ready config for your client at mcp.apify.com. In the agent the tool is named technicaldost--npi-registry-enrichment; ask it, for example, to "run NPI Registry Provider Lookup & Enrichment with {"lastName": "Smith", "state": "CA", "maxItems": 5}".

AI agents without an Apify account can also run and pay for this Actor per request with x402 agentic payments.

Run NPI Registry Provider Lookup & Enrichment via API

Run the Actor and get its results in one call (replace YOUR_APIFY_TOKEN):

curl -X POST "https://api.apify.com/v2/acts/technicaldost~npi-registry-enrichment/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"lastName": "Smith", "state": "CA", "maxItems": 5}'

Python (pip install apify-client):

from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/npi-registry-enrichment").call(run_input={"lastName": "Smith", "state": "CA", "maxItems": 5})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

JavaScript / TypeScript (npm install apify-client):

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/npi-registry-enrichment').call({"lastName": "Smith", "state": "CA", "maxItems": 5});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Long runs: start them with POST /v2/acts/technicaldost~npi-registry-enrichment/runs and fetch the dataset when the run finishes, or receive a webhook.

Integrations

NPI Registry Provider Lookup & Enrichment works with Make, Zapier, n8n, LangChain, Google Sheets, Slack, GitHub and webhooks. Schedule runs in Apify Console and send new results straight to your apps, spreadsheets or AI pipelines.

FAQ

Can I use NPI Registry Provider Lookup & Enrichment with AI agents like Claude or ChatGPT?

Yes. Connect the Apify MCP server with ?tools=technicaldost/npi-registry-enrichment (see above) and the agent can run the Actor and read its results on its own.

Can I call NPI Registry Provider Lookup & Enrichment from my own code?

Yes. Use the REST API, or the official Python and JavaScript clients shown above. Results are available as JSON, CSV, Excel, XML or HTML.

How do I run it on a schedule?

Save your input as a task in Apify Console and add a schedule (for example, daily). Use webhooks or integrations to send each run's results onward.

Is it legal to use this Actor?

It works with publicly available data. Make sure your use complies with the source website's terms and with data protection laws such as GDPR, especially for personal data.

Something doesn't work or I need a feature. What should I do?

Open an issue in the Issues tab on this Actor's page with an example input, and we'll look into it.