# NPI Registry Scraper | Clinic Leads & Profile Changes (`signalfoundryhq/npi-provider-change-radar`) Actor

Search official NPPES provider profiles by specialty and location. Export clinic names, practice addresses, phones and updated profiles. $2 per 1,000 records.

- **URL**: https://apify.com/signalfoundryhq/npi-provider-change-radar.md
- **Developed by:** [Signal Foundry](https://apify.com/signalfoundryhq) (community)
- **Categories:** Automation, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.70 / 1,000 delivered provider profiles

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## NPI Registry Scraper: Clinic Leads & Provider Profile Changes

Search official CMS NPPES records by specialty, organization, name, city, state or postal code. Export normalized clinic and provider profiles to JSON, CSV or Excel, or retrieve them through the Apify API.

**$2 per 1,000 delivered provider profiles ($0.002 each). Platform usage is included. There is no start fee.** With `onlyNew` enabled, previously delivered unchanged record versions are skipped without a result charge. The live Pricing tab is authoritative.

This independent community tool uses public NPPES data. It is not affiliated with CMS, NPPES or HHS.

### What you get

- NPI, organization or provider name, provider type and active status;
- primary specialty and all disclosed taxonomies;
- practice and mailing addresses, public practice phone and fax;
- secondary practice locations, other organization names and authorized official when disclosed;
- public digital endpoints, enumeration date and last update;
- an official NPI Registry link and a stable profile fingerprint.

One result is one provider profile version. Missing source fields remain empty; the tool does not invent email addresses, contact details or credentials.

### Common workflows

- Build a healthcare directory from official organization and specialty records.
- Research clinics by practice location for healthcare supplier market analysis.
- Recheck a list of NPIs and export only profiles that changed.

### Example provider profile

A field subset from a validated run on October 2, 2026. Source records can change; run the Actor for current data.

```json
{
  "npi": "1104014315",
  "providerName": "AB CARDIOLOGY, PLLC",
  "providerType": "Organization",
  "primaryTaxonomy": {
    "code": "207RC0000X",
    "description": "Internal Medicine, Cardiovascular Disease",
    "primary": true,
    "taxonomyGroup": "193400000X - Single Specialty Group"
  },
  "primaryPracticeAddress": {
    "purpose": "LOCATION",
    "type": "DOM",
    "address1": "6624 FANNIN ST STE 1990",
    "city": "HOUSTON",
    "state": "TX",
    "postalCode": "770302330",
    "countryCode": "US",
    "countryName": "United States",
    "phone": "713-436-6653",
    "fax": "713-436-6365"
  },
  "registryUrl": "https://npiregistry.cms.hhs.gov/provider-view/1104014315"
}
```

### Start with a clinic search

```json
{
  "npiNumbers": [],
  "organizationName": "cardiology*",
  "enumerationType": "NPI-2",
  "state": "TX",
  "maxRecordsScanned": 100,
  "onlyNew": false,
  "maxItems": 25
}
```

Use `NPI-2` for organizations and `NPI-1` for individuals. NPPES supports trailing name wildcards such as `cardiology*`. Names may match a DBA or another registered name, so the returned legal name can differ from the search text. Location filters can match a primary or secondary practice address; inspect all returned practice locations.

### Repeated calls without duplicate billing

Set `onlyNew` to `true` and keep the same `stateKey` for the same feed. An unchanged fingerprint is skipped. An update produces a new version containing current source data. No schedule is required.

The comparison covers profile data and the source's last-update fields. It does not provide a field-by-field change report. `resetState` replays current profiles, including result charges.

### API example

```bash
curl -X POST \
  'https://api.apify.com/v2/acts/signalfoundryhq~npi-provider-change-radar/run-sync-get-dataset-items?format=json&maxTotalChargeUsd=0.05' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"npiNumbers":[],"organizationName":"cardiology*","enumerationType":"NPI-2","state":"TX","maxRecordsScanned":100,"onlyNew":false,"maxItems":25}'
```

The spending limit and `maxItems` both bound delivery. A run stops when it cannot afford another result.

### Source limits and interpretation

The official [NPPES API](https://npiregistry.cms.hhs.gov/api-page) uses version 2.1. It returns at most 200 results per request and exposes at most 1,200 matches through skip pagination. Narrow the geography or specialty to cover large searches accurately. This Actor supports up to 100 explicit NPIs in a watchlist.

NPPES is updated daily; source data may be incomplete or outdated. As [CMS explains](https://www.cms.gov/medicare/regulations-guidance/administrative-simplification/data-dissemination), an NPI does not establish that a provider is licensed or credentialed. This tool supplies registry records for directory and research workflows.

### Ready-to-run examples

- [Find Texas cardiology clinic profiles from NPPES](https://apify.com/signalfoundryhq/npi-provider-change-radar/examples/texas-cardiology-clinic-profiles)
- [Find California dental practice profiles from NPPES](https://apify.com/signalfoundryhq/npi-provider-change-radar/examples/california-dental-practice-profiles)
- [Find New York pharmacy profiles from NPPES](https://apify.com/signalfoundryhq/npi-provider-change-radar/examples/new-york-pharmacy-profiles)

# Actor input Schema

## `npiNumbers` (type: `array`):

Optional list of up to 100 ten-digit NPIs. These are looked up in addition to any search filters.

## `enumerationType` (type: `string`):

Filter a search to individual or organizational providers.

## `organizationName` (type: `string`):

Organization search. NPPES supports a trailing wildcard after at least two characters, such as cardiology\*.

## `firstName` (type: `string`):

Individual provider first-name search; \* wildcard supported.

## `lastName` (type: `string`):

Individual provider last-name search; \* wildcard supported.

## `taxonomyDescription` (type: `string`):

Specialty or provider taxonomy, for example Cardiology or Pharmacy; \* wildcard supported.

## `city` (type: `string`):

Practice-location city filter.

## `state` (type: `string`):

Two-letter US state or territory code.

## `postalCode` (type: `string`):

Full or prefix US postal code.

## `countryCode` (type: `string`):

Two-letter country code; defaults to US in NPPES when omitted.

## `includeInactive` (type: `boolean`):

Keep records whose NPPES status is not Active.

## `maxRecordsScanned` (type: `integer`):

NPPES returns at most 200 per request and exposes at most 1,200 per search via skip pagination.

## `stateKey` (type: `string`):

Keep unchanged across scheduled runs; use another key for another provider feed.

## `onlyNew` (type: `boolean`):

Enable for schedules. An unchanged NPI is skipped; material profile changes create a new fingerprint and row.

## `resetState` (type: `boolean`):

Forget saved record fingerprints and replay the current snapshot.

## `maxItems` (type: `integer`):

Stop after this many dataset rows.

## Actor input object example

```json
{
  "npiNumbers": [],
  "enumerationType": "NPI-2",
  "organizationName": "cardiology*",
  "state": "TX",
  "includeInactive": false,
  "maxRecordsScanned": 100,
  "stateKey": "default",
  "onlyNew": false,
  "resetState": false,
  "maxItems": 25
}
```

# Actor output Schema

## `results` (type: `string`):

No description

## `summary` (type: `string`):

No description

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("signalfoundryhq/npi-provider-change-radar").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("signalfoundryhq/npi-provider-change-radar").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{}' |
apify call signalfoundryhq/npi-provider-change-radar --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,signalfoundryhq/npi-provider-change-radar"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/dXzoTschz17649z0I/builds/DKfJMOTPjK9L98EhO/openapi.json