NPI Registry — US Healthcare Provider Lookup (CMS)

Look up US healthcare providers from the official CMS NPI Registry — every doctor, dentist, therapist, pharmacy, hospital and clinic in the US has an NPI. Search by specialty, name, organization, city, or state and get clean, structured JSON: NPI, credentials, specialty, license, address, and phone. Built for healthcare sales, recruiting, provider verification, and B2B data. No API key.

Keywords: NPI registry API, NPI lookup, healthcare provider data, doctor lookup, provider verification, healthcare sales leads, CMS NPI, medical provider directory.

---

Why this actor

The NPPES NPI Registry is the authoritative US directory of healthcare providers, with a free API — but it returns deeply nested records (taxonomies, multiple addresses, identifiers) and paginates with skip/limit. This actor flattens each provider into one clean record and handles paging for you.

• Search every US provider — individuals (NPI-1) and organizations (NPI-2).
• Flexible filters — specialty/taxonomy, state, city, ZIP (wildcards), organization, first/last name, or a direct NPI.
• Clean output — NPI, type, name, credential, primary specialty, license, full location address, phone, status, enumeration date.
• No API key — official CMS NPPES API.

---

What you can build

• Healthcare sales & marketing — build targeted provider lists by specialty + geography.
• Recruiting — find providers by specialty and location.
• Provider verification / credentialing — confirm an NPI, specialty, license, and active status.
• Network & market analysis — map provider density by specialty across regions.
• Data enrichment — resolve provider names to NPIs and structured records.

---

Input

At least one search field is required.

Field	Type	Description
taxonomyDescription	string	Specialty (e.g. Dentist, Cardiology, Pharmacy).
state	string	2-letter US state code.
city	string	City name.
postalCode	string	ZIP (wildcard ok, e.g. 902*).
organizationName	string	Org/practice name (wildcard ok).
firstName / lastName	string	Individual provider name.
npiNumber	string	Look up a specific 10-digit NPI.
maxResults	integer	Max providers (registry caps a query at 1,200).

Example

{ "taxonomyDescription": "Cardiology", "state": "NY", "city": "New York", "maxResults": 500 }

---

Output

{
  "npi": "1760813802",
  "type": "Organization",
  "name": "101 DENTAL GROUP",
  "credential": null,
  "status": "Active",
  "primary_specialty": "Dentist, General Practice",
  "taxonomy_code": "1223G0001X",
  "license": "54634",
  "license_state": "CA",
  "address": "7259 OWENSMOUTH AVE",
  "city": "CANOGA PARK",
  "state": "CA",
  "postal_code": "913031530",
  "phone": "818-999-9900",
  "enumeration_date": "2013-11-27",
  "scraped_at": "2026-06-12T00:00:00.000Z"
}

A final {"_type":"summary"} record reports how many providers were returned.

---

Pricing

First 25 providers free per account, then $0.003 per provider. Zero charge on empty searches. No monthly rental, no API key.

---

FAQ

Do I need a key? No — the CMS NPI Registry API is fully open.

Individuals and organizations? Both — NPI-1 (individuals) and NPI-2 (organizations), labeled in the type field.

How many results per search? The registry caps a single query at 1,200 (paged). Narrow by city/specialty for larger universes.

Can I verify one NPI? Yes — pass npiNumber for a direct lookup.

Use in Claude, ChatGPT & any MCP agent

This actor is also a Model Context Protocol (MCP) server tool — call it directly from Claude, ChatGPT, Cursor, Windsurf, or any MCP-compatible AI agent. The agent only pays for results delivered (same pay-per-result model).

• Per-actor MCP endpoint: https://mcp.apify.com/?tools=themineworks/npi-registry-healthcare
• Full Mine Works MCP server (all tools): https://the-mine-works-mcp.hatchable.site/api/mcp

// Call this actor as a tool via apify-client (Node)
import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('themineworks/npi-registry-healthcare').call({ /* input from the table above */ });
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);