US Healthcare Provider Search — CMS NPI Registry

Search and verify US healthcare providers and organizations in the public CMS NPPES NPI Registry. Find records by exact NPI, person or practice name, specialty, city, state, ZIP, or provider type and receive normalized data ready for API and automation workflows.

No upstream API key is required.

Quick start

1. For an exact lookup, enter a 10-digit NPI.
2. For discovery, combine name / organization / specialty / location filters.
3. Set the maximum number of results and click Start.

The Input tab is prefilled with Dentist + Miami, FL so you can test the Actor immediately.

Example input — specialty and location

{
  "taxonomyDescription": "Dentist",
  "city": "Miami",
  "state": "FL",
  "maxResults": 10
}

Example input — exact NPI

{
  "npi": "1659375291",
  "maxResults": 1
}

What you get

Each dataset row is a normalized CMS NPPES record containing:

• NPI and provider / organization name,
• individual vs organization type (NPI-1 / NPI-2),
• provider status and dates,
• primary taxonomy plus all reported taxonomies,
• practice and mailing addresses,
• additional practice locations when available,
• canonical CMS provider link.

Common workflows

• Provider verification: exact NPI → current NPPES identity and taxonomy.
• Practice discovery: organization name + city/state.
• Specialty lists: taxonomy + location, for example dentists in Miami or cardiology in California.
• Data enrichment: use an NPI from your CRM and join the returned normalized fields.

Pricing

$0.0025 per provider result delivered to the default dataset (Pay per event).

API & automation

Use the Actor through HTTP API, Python, JavaScript, CLI, OpenAPI or MCP. The API tab provides ready-to-copy examples using the same fields shown in the Input tab.

Data source and limits

Source: CMS NPPES NPI Registry API v2.1. This Actor is designed for bounded interactive searches and returns up to 1,200 results per search bucket. For millions of records, use the official NPPES bulk files instead of repeated Registry API queries.

Important: an NPI identifies a provider in NPPES; it does not prove professional licensure or credentialing.

Support

Open the Issues tab with your filters and run ID if a query behaves unexpectedly. Never include Apify tokens or private credentials.