# Healthcare Provider Verification — NPPES/NPI (`alaudinburki/provider-verification`) Actor

Verify a healthcare provider's NPI registration status, specialty (taxonomy), and practice location from CMS's free official NPPES registry. Covers both individual and organization NPIs. No key required.

- **URL**: https://apify.com/alaudinburki/provider-verification.md
- **Developed by:** [alaudin burki](https://apify.com/alaudinburki) (community)
- **Categories:** Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Healthcare Provider Verification — NPPES/NPI

Credentialing services, insurance networks, and patients currently verify
a healthcare provider's NPI (National Provider Identifier) status by
hand, on CMS's own NPPES lookup. Free, public, keyless. This turns a
name/NPI/organization search into a verified provider record: active
status, specialty, and practice address.

### Input

```json
{ "providers": [{ "organizationName": "Mayo Clinic" }] }
```

Query by `npi`, `organizationName`, or `firstName`/`lastName` — one
identifying field is required per entry; `state` is optional to narrow results.

### Sample output

```json
{
  "npi": "1881018208",
  "enumerationType": "NPI-2",
  "name": "MAYO CLINIC",
  "isOrganization": true,
  "status": "A",
  "isActive": true,
  "practiceCity": "ROCHESTER",
  "practiceState": "MN"
}
```

### Typical uses

- **Credentialing / provider network verification** — confirm an NPI is
  active and matches the claimed specialty before onboarding.
- **Insurance network validation** — bulk-check a provider roster's NPI status.
- **Patient due diligence** — verify a provider's credentials before a visit.
- **Fraud/compliance screening** — a deactivated or mismatched NPI is a
  real signal worth investigating.

### Pricing

**$0.002 per provider record.**

### ⚠️ Read before you act

- **Covers both individual (NPI-1) and organization (NPI-2) providers** —
  `isOrganization` tells you which; a search by organization name naturally
  returns NPI-2 records, a name search returns NPI-1.
- **`isActive` reflects NPPES's own current status** — deactivation isn't
  necessarily fraud; providers retire, close practices, or merge
  organizations. Treat it as a signal to investigate, not a verdict.
- **The practice address is the LOCATION address**, not the mailing
  address, when both are on file — the one relevant to "where do they
  actually practice."

### FAQ

- **Do I need an API key?** No — NPPES's registry API is free and keyless.
- **What's the difference between NPI-1 and NPI-2?** NPI-1 is an
  individual provider (a doctor, nurse, therapist); NPI-2 is an
  organization (a clinic, hospital, group practice).
- **Can I search by license number?** Not directly — NPPES doesn't expose
  a license-number search parameter; search by name/NPI/organization and
  check the returned `licenseNumber` field instead.

### Related actors

- **Nonprofit Financial Lookup** — the same official-registry-verification
  pattern, for nonprofit financial data instead of healthcare credentials.
- **Financial Complaint Monitor** — another regulated-entity lookup, for
  CFPB financial company complaints.

# Actor input Schema

## `providers` (type: `array`):

Providers to look up, each with npi, organizationName, or firstName/lastName (state optional to narrow). Example: \[{"npi": "1063837144"}] or \[{"organizationName": "Mayo Clinic"}]

## `maxResultsPerQuery` (type: `integer`):

How many matching providers to return per query.

## Actor input object example

```json
{
  "providers": [
    {
      "organizationName": "Mayo Clinic"
    }
  ],
  "maxResultsPerQuery": 10
}
```

# Actor output Schema

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

Matched providers, active first.

## `qualityReport` (type: `string`):

Queries checked, active/inactive counts, problems.

# 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 = {
    "providers": [
        {
            "organizationName": "Mayo Clinic"
        }
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("alaudinburki/provider-verification").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 = { "providers": [{ "organizationName": "Mayo Clinic" }] }

# Run the Actor and wait for it to finish
run = client.actor("alaudinburki/provider-verification").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 '{
  "providers": [
    {
      "organizationName": "Mayo Clinic"
    }
  ]
}' |
apify call alaudinburki/provider-verification --silent --output-dataset

```

## MCP server setup

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

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/aBJIuY3q0bTtsMl8i/builds/PywEVXsQoa7dTATX8/openapi.json