NPI Registry Scraper: US Healthcare Providers avatar

NPI Registry Scraper: US Healthcare Providers

Pricing

$3.00 / 1,000 providers

Go to Apify Store
NPI Registry Scraper: US Healthcare Providers

NPI Registry Scraper: US Healthcare Providers

Scrape US healthcare providers from the official CMS NPI Registry by specialty, name, org, city or state. Get NPI, credentials, specialty, license, address, phone as clean JSON. No API key. Works in Claude, ChatGPT and any MCP agent.

Pricing

$3.00 / 1,000 providers

Rating

0.0

(0)

Developer

The Mine Works

The Mine Works

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

2

Monthly active users

a day ago

Last modified

Categories

Share

๐Ÿฉบ NPI Registry Scraper: US Healthcare Provider Data (No API Key)

Overview

NPI Registry Scraper pulls verified US healthcare provider records straight from the official CMS National Provider Identifier registry. Search by specialty, name, organisation, city, state, or ZIP code and get back structured JSON with NPIs, credentials, taxonomy, license numbers, practice addresses, and phone numbers. No API key, no signup, no per-seat pricing.

It's the fastest way to build a targeted list of doctors, dentists, therapists, pharmacies, or hospitals for outreach, referral mapping, market sizing, or credentialing. The registry is the single source of truth for US healthcare identifiers, so every record you get is billable-grade data.

Reliability posture: blocked, empty, or failed runs are never charged. You only pay for a provider record that was actually delivered.

โœ… No login required | โœ… No API key | โœ… Pay only for providers returned | โœ… MCP-ready for AI agents

Features

Specialty search. Pull every dentist in California or every cardiologist in Manhattan in one run. Organisation search. Wildcard match hospitals, clinics, and pharmacies by name. Individual lookup. Query by first name, last name, or a specific 10-digit NPI. Geo filters. Restrict by state code, city, or ZIP (wildcards supported for ZIP prefixes). Clean output. NPI, credentials, taxonomy code, license, address, phone, fax as flat JSON fields.

How it works

The actor calls the official CMS NPI Registry API (npiregistry.cms.hhs.gov), which is the authoritative source for every provider that bills Medicare or Medicaid in the United States. It doesn't scrape a third-party mirror, so every field matches what CMS itself publishes.

Each search request is scoped by your input filters (specialty, geo, name), paginated up to the CMS single-query cap of 1,200 records, and normalised into flat fields ready for a CRM or database. Records without a required field are still returned so you can decide how to handle partial data downstream.

๐Ÿงพ Input configuration

{
"taxonomyDescription": "Dentist",
"state": "CA",
"city": "Los Angeles",
"maxResults": 200
}

๐Ÿ“ค Output format

{
"npi": "1932088416",
"type": "Individual",
"name": "AZITA HAJ HOSSEIN TALASAZ",
"credential": "PharmD, PhD",
"status": "Active",
"primary_specialty": "Pharmacist, Cardiology",
"taxonomy_code": "1835C0206X",
"license": "071090",
"license_state": "NY",
"address": "622 W 168TH ST APT 5C",
"city": "NEW YORK",
"state": "NY",
"postal_code": "100323720",
"phone": "212-305-2500",
"enumeration_date": "2025-08-29",
"last_updated": "2025-08-29",
"scraped_at": "2026-07-15T04:15:43.911Z"
}

Every provider record contains these fields:

FieldDescription
๐Ÿ†” npi10-digit National Provider Identifier
๐Ÿ‘ค typeIndividual or Organization
๐Ÿ™‹ nameFull name for individuals, organisation name for entities
๐ŸŽ“ credentialProfessional credentials (MD, DO, DDS, RN, PharmD, etc.)
โœ… statusActive or inactive
๐Ÿฉบ primary_specialtyPrimary specialty description from CMS taxonomy
๐Ÿ”– taxonomy_code10-character NUCC taxonomy code
๐Ÿ“œ licenseState license number if published
๐Ÿ›๏ธ license_stateState that issued the license
๐Ÿข addressStreet address of practice location
๐Ÿ™๏ธ cityPractice city
๐Ÿ—บ๏ธ statePractice state (2-letter)
๐Ÿ“ฎ postal_codePractice ZIP
๐Ÿ“ž phonePractice phone number
๐Ÿ“† enumeration_dateDate the NPI was first issued
๐Ÿ•’ last_updatedDate CMS last updated this record

๐Ÿ’ผ Common use cases

Healthcare sales & marketing Build targeted lists of specialists to reach with pharma, medical device, or SaaS outreach. Filter by state and specialty to plan a rep territory or a regional launch.

Provider directory & referral mapping Populate an in-house directory or referral tool with authoritative CMS data. Cross check the specialty and license of a doctor before adding them to a network.

Credentialing & compliance Verify NPI, taxonomy, and license against the CMS source of truth. Pull a monthly refresh of active providers in a given state for compliance audits.

Market research Size a market by counting active providers per specialty per state. Track new registrations and status changes over time.

๐Ÿš€ Getting started

  1. Open the actor and add a specialty (e.g. Dentist, Cardiology, Pharmacy).
  2. Add a state code (CA, NY, TX) and optionally a city or ZIP to narrow the search.
  3. Set max providers (default 200, hard cap 1,200 per query).
  4. Click Start. Results stream to the dataset as they're fetched.
  5. Download as JSON, CSV, or Excel, or pull the dataset via API or MCP into your CRM.

FAQ

Where does the data come from? Directly from the official CMS NPI Registry at npiregistry.cms.hhs.gov. This is the same registry that Medicare and Medicaid use to verify providers, so the data is authoritative and updated continuously.

Is there a rate limit? CMS caps a single query at 1,200 results. To pull more than 1,200 providers in one specialty, split your search by state or city and run several queries.

How much does it cost? Pay per provider returned. Cheap enough to build a national provider database, priced to be used often. No subscription, no seat license, no monthly minimum.

Can I use it in an AI agent? Yes. It's exposed as an MCP tool. See below.

Use in Claude, ChatGPT & any MCP agent

https://mcp.apify.com/?tools=themineworks/npi-registry-healthcare

Or call it programmatically with the Apify client:

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('themineworks/npi-registry-healthcare').call({
taxonomyDescription: 'Dentist',
state: 'CA',
maxResults: 200,
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

๐Ÿ› ๏ธ Complete your healthcare data pipeline

Pulled the providers. Now enrich and act on them with the rest of the suite:

Typical flow: NPI Registry finds the providers, website-contact-finder adds practice-level contact info, email-verifier-validator confirms deliverability.

Questions or need a custom field set? Reach out through the Apify profile.