← All agent tools

Healthcare data CMS (U.S. Centers for Medicare & Medicaid Services)

NPPES NPI Registry API

Search the public US provider identifier registry by NPI, provider name, specialty or location.

Source review: 2026-10-28 · Imported: 1 November 2026

A practical starting point

What could you build?

A directory assistant can retrieve the registry entry associated with a provider identifier.

Before you connect

An NPI is an identifier, not proof of a current licence or clinical qualifications. Keep queries modest and check the source record.

Capabilities & requirements

Dated specifications from the licensed source dataset. “Not published” indicates missing information, rather than confirmed absence.

NPPES NPI Registry API specifications
CapabilityDetails and source
Statusv2.1 current; 1.0/2.0 retired

Version 2.1 has no planned phase-out date; calls without a version flag no longer work.

Source (external) · Verified 2026-10-28 on https://npiregistry.cms.hhs.gov/api-page
API key requiredNo key

Keyless GET returned HTTP 200 on 2026-10-28.

Source (external) · Verified 2026-10-28 by test request to https://npiregistry.cms.hhs.gov/api/?version=2.1&number=1003000126
Free tierFree

CMS says there is no charge to view the registry or download the files.

Source (external) · Verified 2026-10-28 on https://www.cms.gov/medicare/regulations-guidance/administrative-simplification/data-dissemination
Rate limitNot published

Hourly query cap since June 25, 2024, number not published; bulk use must use the download files. 200 results per request, skip up to 1,000.

Source (external) · Not published by vendor: checked 2026-10-28 on https://npiregistry.cms.hhs.gov/help-api
Official MCP serverNot published

No MCP server from CMS; only the REST API and downloadable files.

Source (external) · Not published by vendor: checked 2026-10-28 on https://npiregistry.cms.hhs.gov/api-page
Official SDKNot published

No official SDK; the API is plain HTTPS GET with query fields.

Source (external) · Not published by vendor: checked 2026-10-28 on https://npiregistry.cms.hhs.gov/api-page
Data license / termsFOIA public record

CMS must disclose this data under FOIA; no separate API terms or data license is published.

Source (external) · Verified 2026-10-28 on https://www.cms.gov/medicare/regulations-guidance/administrative-simplification/data-dissemination
Commercial use allowedNot published

No commercial-use rule is published; the data is public record released at no charge.

Source (external) · Not published by vendor: checked 2026-10-28 on https://www.cms.gov/medicare/regulations-guidance/administrative-simplification/data-dissemination
CORS / browser useNo CORS header

GET and preflight with a third-party Origin on 2026-10-28 returned no Access-Control-Allow-Origin.

Source (external) · Verified 2026-10-28 by test request to https://npiregistry.cms.hhs.gov/api/?version=2.1&number=1003000126
Freshness / coverageDaily from NPPES

The API retrieves data from NPPES daily; search pages cap at the first 2,100 results.

Source (external) · Verified 2026-10-28 on https://npiregistry.cms.hhs.gov/api-page

Operational reference

Additional facts and qualifications retained from AgentAPIList’s CC BY 4.0 dataset, with provider references.

Price

Free. CMS says there is no charge to view the registry or download the files.

Provider reference (external)

API key / auth

None. Our keyless GET requests on 2026-10-28 returned HTTP 200.

Provider reference (external)

Rate limit

Since June 25, 2024, NPPES limits how many registry queries can run per hour, but publishes no number; bulk lookups must use the downloadable file. Our responses carried no rate-limit headers.

Provider reference (external)

Result caps

Up to 200 results per request (limit, default 10) and skip up to 1,000, so at most 1,200 records for one search over six requests.

Provider reference (external)

License / terms

The data is FOIA-disclosable public record that CMS is required to publish; providers with active NPIs cannot opt out. CMS publishes no separate API terms or data license.

Provider reference (external)

Version status

Version 2.1 is current with no planned phase-out date; 1.0, 2.0 and calls without a version flag no longer work.

Provider reference (external)

Search rules

state cannot be the only criterion (error 07 “requires additional search criteria” in the source publisher’s test), enumeration_type needs another field, and names allow a trailing * after two characters.

Provider reference (external)

Setup references

HTTP request example

Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.

curl -sS "https://npiregistry.cms.hhs.gov/api/?version=2.1&number=1003000126"
Agent connection example

Adapted from the attributed source dataset. Review before running; these examples were not executed by Tech in General.

// Tool definition for Claude, OpenAI or any function-calling agent
{
  "name": "npi_lookup",
  "description": "Look up US health care providers in the CMS NPPES NPI Registry (read-only, no key). Give an NPI number, or a name plus a state or city.",
  "input_schema": {
    "type": "object",
    "properties": {
      "number": { "type": "string", "description": "Exactly 10 digits" },
      "first_name": { "type": "string" },
      "last_name": { "type": "string" },
      "organization_name": { "type": "string" },
      "taxonomy_description": { "type": "string" },
      "city": { "type": "string" },
      "state": { "type": "string", "description": "2-letter code; never the only field" },
      "limit": { "type": "integer", "maximum": 200 }
    }
  }
}
// Implementation: GET https://npiregistry.cms.hhs.gov/api/?version=2.1&<fields>

A tool schema needs an HTTP implementation; it does not by itself install an MCP server. Keep credentials out of browser code.

Other connections to explore

Back to the full directory →

Source & reuse

Download the complete licensed source snapshot (JSON), including the original source’s caveats, alternative notes and examples.