Do I need an API key or an account elsewhere?

No. It reads CMS's free public NPPES registry.

Healthcare Provider Verification — NPPES/NPI

alaudin burki · @alaudinburki

Verify US healthcare providers by NPI in CMS's official NPPES registry: status, specialty, taxonomy and practice address, for individuals and organisations.

Lead generation Automation Developer tools

About

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

{ "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

{
  "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.

⚠️ 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."

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.

Limitations

Healthcare Provider Verification reads only what its sources publish publicly. Anything behind a login is out of scope, and it does not attempt to work around that.
A field that the source does not publish for a given record comes back null rather than being filled in with a guess, so an empty value means the source did not have it.
Output quality is bounded by the source. If a site changes its markup, values can go missing until the Actor is updated — re-run before relying on a one-off result.
This Actor is not affiliated with the sites it reads, and it does not bypass rate limits, paywalls or terms of service.

Fields

Field	Type	What it holds
`matchedQuery`	string,null	The query this row matched.
`npi`	string,null	National Provider Identifier.
`enumerationType`	string,null	How the identifier was assigned.
`name`	string,null	Display name as the source writes it.
`isOrganization`	boolean,null	Whether the address belongs to an organisation rather than a person.
`status`	string,null	Outcome recorded for this row.
`isActive`	boolean,null	Whether the record is still active at the source.
`credential`	string,null	Credential this row describes.
`primarySpecialty`	string,null	Primary Specialty as recorded for this row.
`licenseNumber`	string,null	Licence number.
`licenseState`	string,null	State that issued the licence.
`practiceCity`	string,null	City where the practice is located.
`practiceState`	string,null	State where the practice is located.
`practicePhone`	string,null	Phone number for the practice.
`enumerationDate`	string,null	Date the identifier was assigned.
`lastUpdated`	string,null	ISO 8601 timestamp of the last change seen.
`verdict`	string,null	The Actor's conclusion for this row, stated in words.

Pricing

The price and any free trial are shown in the pricing panel on this page. Compute is billed from your prepaid Bytewells credits.

FAQ

What does Healthcare Provider Verification return?: Verify US healthcare providers by NPI in CMS's official NPPES registry: status, specialty, taxonomy and practice address, for individuals and organisations.
Do I need an API key or an account elsewhere?: No. It reads CMS's free public NPPES registry.
How am I billed?: The price and any free trial are shown in the pricing panel on this page. Compute is billed from your prepaid Bytewells credits, and a run that returns nothing costs only its compute.

Healthcare Provider Verification — NPPES/NPI price

Start with one monthly volume— 100,000 rows. The chart compares Bytewells (rent plus usage from recent runs, compute and platform proxy) with Apify on each plan. Bars are result charges only; Apify platform fees are in the table below.

100,000 rows a month

Cheaper for high-volume use above 10,000 rows a month. Apify is cheaper under 10,000 rows/mo.

Cost per 1,000 rows

The estimate on the card is about $0.04 per 1,000 rows from recent settled runs (compute at 0.25 CU, or $0.04, plus platform proxy when the Actor uses it). A compute unit is 1 GB of memory for one hour, at $0.15.

Throughput

Throughput from the same recent succeeded runs, counted the other way. Startup stays in the time, so a long run returns rows a little faster than this.

Results per CU: 4,000
Results per minute: 66.7

Monthly cost against Apify

Bytewells is monthly rental plus usage, with no platform commitment. Apify charges a plan fee plus per-result usage. The cost column is only that usage at the row count below; commitments are the platform subscription.

Healthcare Provider Verification — NPPES/NPI monthly cost at 100,000 rows
100,000 rows a month	Monthly commitment	Usage cost
Bytewells	No commitment	$15.75
Bytewells rental	—	$12
Bytewells usage	—	$3.75
Bytewells compute (est.)	—	$3.75
Apify Free	$0	$200
Apify Starter	$19/mo	$200
Apify Scale	$199/mo	$200
Apify Business	$999/mo	$200

How this estimate is made

The cost per 1,000 rows divides the compute from recent succeeded runs in the last 90 days by the rows those runs returned. Startup time on a short run stays in the rate, so a long month is priced a little high. The median and the 99th percentile are per-run rates from the same window.

Honest verdict

10,000

rows a month

This is the breakeven number.

Occasional user

Under 10,000 rows a month, Apify is cheaper.

See it on Apify

Power users

Power users above 10,000 rows a month cost less here.

Input

Preview of the input form. Rent the Actor to fill it in and start runs from the console.

Fields

Providers

providers

json

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

Max results per query

maxResultsPerQuery

1–50

How many matching providers to return per query.

API

Bytewells speaks the Apify API. Existing integrations keep working: point apify-client at https://bytewells.com/api and use your Bytewells API token (Console → Settings → API access). The Actor ID is alaudinburki/provider-verification (or alaudinburki~provider-verification in URLs).

JavaScript · apify-client

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({
  token: process.env.BYTEWELLS_TOKEN,
  baseUrl: 'https://bytewells.com/api',
});

const input = {
  "providers": [
    {
      "organizationName": "Mayo Clinic"
    }
  ],
  "maxResultsPerQuery": 10
};

const run = await client.actor('alaudinburki/provider-verification').call(input);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python · apify-client

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ["BYTEWELLS_TOKEN"], api_url="https://bytewells.com/api")

run_input = {
    "providers": [
        {
            "organizationName": "Mayo Clinic"
        }
    ],
    "maxResultsPerQuery": 10
}

run = client.actor("alaudinburki/provider-verification").call(run_input=run_input)
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)

HTTP · curl

curl -X POST "https://bytewells.com/api/v2/acts/alaudinburki~provider-verification/runs" \
  -H "Authorization: Bearer $BYTEWELLS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"providers":[{"organizationName":"Mayo Clinic"}],"maxResultsPerQuery":10}'

Runs are billed as compute from your credit balance. Paid Actors need an active rental or trial; otherwise the API answers 402 rental-required.

More Actors from the same publisher.

View all from @alaudinburki

Healthcare Provider Verification — NPPES/NPI

About

Healthcare Provider Verification — NPPES/NPI

Input

Sample output

Typical uses

⚠️ Read before you act

Related actors

Limitations

Fields

Pricing

FAQ

Healthcare Provider Verification — NPPES/NPI price

Cost per 1,000 rows

Throughput

Monthly cost against Apify

How this estimate is made

Honest verdict

Input

Fields

Providers

Max results per query

API

JavaScript · apify-client

Python · apify-client

HTTP · curl

ATS Jobs Multi-Board — Greenhouse, Workday, Lever, Ashby & more

Company Due Diligence — 7 Registries + Sanctions Screen

Lead Finder — Named Contacts & Verified Emails

REST API Fetcher & Paginator — Any JSON API to Dataset

Google Maps Places — Address, Phone, Rating and Hours

iTunes & App Store Search — Apps, Podcasts, Media