Skip to content
healthcare.dev

US healthcare reference data, for humans and agents.

Official CMS, FDA, NLM and HHS OIG sources, normalized, joined and kept current, in one API your code and your agents can cite. Fresh, cited, dead simple.

The API

One request, every answer cited.

One call (Pro) checks a provider against the NPI registry, Medicare enrollment, opt-out and OIG exclusions, flags where sources disagree, and cites each release in meta. Every response is the same envelope; errors are RFC 9457 problem details your code and your agents can branch on.

curl "https://api.healthcare.dev/v1/providers/1922074434/full?view=compact" \
  -H "Authorization: Bearer $HDEV_API_KEY"
200 OK · application/json
{
  "data": {
    "npi": "1922074434",
    "name": "MAYO CLINIC",
    "status": "active",
    "practice_location": {
      "city": "ROCHESTER",
      "state": "MN",
      "postal_code": "559050001"
    },
    "flags": {
      "medicare_enrolled": true,
      "opted_out": false,
      "exclusion_recorded": false,
      "possible_exclusion_match": false,
      "unverified_exclusion_match": false
    },
    "exclusion_note": "Matched by NPI as listed in the OIG file (LEIE). Most LEIE records carry no NPI, so an empty answer means no e...",
    "missing": [
      {
        "component": "opt_out",
        "status": "not_listed",
        "reason": "Matched by NPI in CMS's Opt Out Affidavits file, release 2026-09-01. Not listed means no opt-out affidavit rec..."
      },
      {
        "component": "exclusion",
        "status": "not_listed",
        "reason": "Matched by NPI as listed in the OIG file (LEIE). Most LEIE records carry no NPI, so an empty answer means no e..."
      },
      {
        "component": "exclusion_matches",
        "status": "not_listed",
        "reason": "No possible match for this NPI among the OIG records that list no NPI (LEIE file of 2026-10-09): matching need..."
      }
    ],
    "conflicts": []
  },
  "meta": {
    "source": "cms-npi-registry+cms-pecos-enrollment+cms-opt-out+hhs-oig-leie",
    "data_version": "npi-registry@registry-live-2026-11-01,medicare-enrollment@2026-10-01,medicare-opt-out@2026-09-01,oig-exclusion...",
    "license": "Public domain (CMS NPI Registry) | Public domain (CMS, data.cms.gov) | Public domain (CMS, data.cms.gov) | Pub..."
  }
}

The data

21 official sources, one schema

Straight from CMS, FDA, NLM and HHS OIG: reloaded on every release, held back unless release gates pass, versioned with history, and joined across sources with conflicts flagged. Live version numbers below.

Without us, with us

A model alone answers from memory. With us, it cites.

Model alone

  • No source, release or date to show for its answer
  • Can't see what changed after its training: new codes, this week's recalls, this month's exclusions
  • Guesses when it doesn't know, and sounds just as sure

With healthcare.dev

  • Answers from the current release, with source, data_version and license in every response
  • Reads the latest CMS, FDA, NLM and OIG releases, checked by release gates before they serve
  • Says "not listed" when a source has no record, instead of guessing

On our benchmark of 53 healthcare reference questions, the best-scoring model answered 98.1% correctly with these tools and 94.3% alone. See every model and run →

For agents

Built for the agents that will call it.

33 read-only MCP tools that map to what agents actually do. Compact, capped results with sources, so answers come with citations. Docs agents can read: llms.txt, a Markdown copy of every page, and a SKILL.md.

  • lookup_code
  • search_codes
  • search_by_meaning
  • find_care_category
  • explain_code_hierarchy
  • lookup_drug
  • search_drugs
  • map_ndc_to_rxnorm
  • get_drug_full
  • get_drug_price
  • check_drug_recalls
  • check_drug_shortages
  • get_drug_label
  • get_medicare_asp
  • lookup_provider
  • search_providers
  • validate_npi
  • check_provider_exclusion
  • check_medicare_enrollment
  • check_medicare_opt_out
  • get_provider_full
  • get_provider_ownership
  • check_medicare_coverage
  • check_prior_auth
  • find_marketplace_plans
  • get_marketplace_plan
  • find_payers
  • get_payer_prior_auth_metrics
  • get_policy_history
  • check_ma_internal_criteria
  • list_datasets
  • report_issue
  • get_dataset_changes
claude.ai · Claude Desktop · Cursor · VS Code
Add a connector with this URL, click Connect, sign in:

https://mcp.healthcare.dev/mcp
Claude Code
claude mcp add --transport http healthcare-dev https://mcp.healthcare.dev/mcp

How it stays current

A pipeline, not a spreadsheet.

  1. 01

    Detect

    Watch CMS, FDA, NLM, HHS OIG and payers for new releases

  2. 02

    Validate

    Schema, row counts and golden records must pass

  3. 03

    Version

    Publish an immutable release; keep history

  4. 04

    Serve

    REST and MCP, cited every time

01

One schema

Codes, drugs, providers and coverage from CMS, FDA, NLM and HHS OIG come back in the same envelope, with the same lifecycle fields and the same errors.

02

Versioned

Every upstream release is loaded, tested and published as an immutable version. Ask for a code as it was on any date.

03

Cited

Every response names its source, release and license, so an agent can show its work and a person can check it.

04

No PHI

Reference data only. We never accept patient information, so there's no BAA to sign and no HIPAA scope to inherit.

Examples

What you can build

App ideas with working code and the datasets behind them.

Pricing

Public prices, no sales call.

Start free with 1,000 calls a month. Every plan includes every core dataset, the REST API and the MCP server. Pay annually and get 2 months free.

Questions

Frequently asked

What is healthcare.dev?
A developer API for US healthcare reference data: ICD-10-CM, ICD-10-PCS and HCPCS Level II codes; drugs (the FDA NDC Directory, RxNorm, FDA labels, recalls and shortages, NADAC and Medicare Part B prices); providers (NPI, Medicare enrollment and opt-out, OIG exclusions and ownership); Medicare coverage support; and payer prior authorization metrics. It is available as a REST API with an OpenAPI spec and as an MCP server for AI agents.
Is there a free plan?
Yes. The Free plan includes 1,000 calls a month with no card, and stops at that cap. Paid plans start at $29/mo with more calls, a low per-call price after that and a spend cap you set.
How much does it cost?
Free $0 for 1,000 calls/mo, Builder $29/mo for 25,000 calls/mo, Pro $199/mo for 100,000 calls/mo. Pay annually and get 2 months free. Prices are public and the same for everyone, and MCP calls cost the same as REST calls.
Does healthcare.dev handle patient data?
No PHI: the API serves reference data only and must never receive patient information. That keeps it outside HIPAA business associate scope.
Can AI agents use it?
Yes. The remote MCP server at mcp.healthcare.dev works with Claude, Cursor, VS Code and Codex, and the docs publish llms.txt and Markdown versions of every page.
Is this medical advice?
No. healthcare.dev is reference data, not medical, coding or billing advice.

Your first call, in two minutes.

Sign up, copy a key, paste one line. No card, no sales call.

curl https://api.healthcare.dev/v1/codes/icd10cm/E11.9 -H "Authorization: Bearer $HDEV_API_KEY"