Skip to content
healthcare.dev

US healthcare reference data, for humans and agents.

ICD-10 HCPCS NDC RxNorm and NPI in one consistent, versioned, cited API. Free to start, no sales call.

5,000 free calls a month · no card · first call in under two minutes

The API

One request, every answer cited.

Every response is the same envelope: the record in data, and its source, release and license in meta. Errors are RFC 9457 problem details your code and your agents can branch on.

curl https://api.healthcare.dev/v1/codes/icd10cm/E11.9 \
  -H "Authorization: Bearer $HDEV_API_KEY"
200 OK · application/json
{
  "data": {
    "system": "icd10cm",
    "code": "E11.9",
    "display": "Type 2 diabetes mellitus without complications",
    "billable": true,
    "parent": "E11",
    "status": "active",
    "effective_start": "2015-10-01",
    "effective_end": null
  },
  "meta": {
    "source": "cms-icd10",
    "data_version": "2026.1",
    "retrieved_at": "2026-10-24T12:00:00Z",
    "license": "Public domain (CMS)"
  }
}

The data

Six public datasets, kept current

Loaded from the source on every release, normalized into one schema and served with live version numbers.

For agents

Built for the agents that will call it.

Nine 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
  • explain_code_hierarchy
  • lookup_drug
  • search_drugs
  • map_ndc_to_rxnorm
  • validate_npi
  • list_datasets
  • get_dataset_changes
Claude Code
claude mcp add --transport http healthcare-dev \
  https://mcp.healthcare.dev/mcp \
  --header "Authorization: Bearer $HDEV_API_KEY"
~/.cursor/mcp.json
{
  "mcpServers": {
    "healthcare-dev": {
      "url": "https://mcp.healthcare.dev/mcp",
      "headers": { "Authorization": "Bearer hdev_live_..." }
    }
  }
}

How it stays current

A pipeline, not a spreadsheet.

  1. 01

    Detect

    Watch CMS, FDA and NLM 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, MCP, SDK and CLI, cited every time

01

One schema

Codes, drugs and providers from CMS, FDA and NLM 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

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

Free tools

Try it without a key

Questions

Frequently asked

What is healthcare.dev?
A developer API for US healthcare reference data: ICD-10-CM and ICD-10-PCS codes, HCPCS Level II, the FDA NDC Directory, RxNorm and, soon, NPI providers. It is available as REST, an MCP server for AI agents, a TypeScript SDK and a CLI.
Is there a free plan?
Yes. The Free plan includes 5,000 calls a month with no card. Pay as you go removes the cap and bills per call.
Does healthcare.dev handle patient data?
No. The API serves public reference data 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"