All recipes

One page per job: which endpoints to call, in what order, on which plan, with curl, TypeScript, Python and an MCP prompt.

Each recipe starts from a job, not a dataset, and joins the endpoints that answer it. Every recipe has the same parts: the plan it needs, the calls (curl, TypeScript, Python), a prompt for an agent with the MCP server connected, how to read the answer, and what the answer is not.

Verify a provider

NPI, Medicare enrollment, opt-out, OIG exclusions and source conflicts, before you schedule or pay. Free; one call on Pro.

Check Medicare coverage

Does a local coverage document list this diagnosis as supporting this code, in this state? Pro.

Drug safety status

NDC to RxNorm, FDA shortage, open recalls and the boxed warning. Free; one call on Pro.

Compare payers' prior auth metrics

Approval, denial, appeal and turnaround rates as each plan posts them. Builder.

Check a prior auth requirement (preview)

Does this payer's list require prior authorization for this code, per line of business? Pro, not available yet.

Check MA internal criteria (preview)

Which services a Medicare Advantage plan covers with its own criteria, with links. Pro, not available yet.

Keep your data fresh

Release list, change feed and signed webhooks, so a local copy or cache never goes stale. Every plan to Pro.

Ground an agent

Connect the MCP server, give the agent a system prompt, and cite meta in every answer. Every plan.

Before you start

A key. Every call needs one: a Free key from app.healthcare.dev works for the Free recipes (Quickstart). Set it as HDEV_API_KEY; the SDKs and the local MCP server read it from there.
Plans. Free and Builder can try the features their plan doesn't include: 50 preview calls a month on Free, 200 on Builder, per feature (previews). Past that, a call answers 403 plan-upgrade-required with the plan that does and a one-click upgrade_url (the SDKs raise PlanUpgradeRequiredError).
SDKs. TypeScript: npm i @healthcare.dev/sdk. Python: install from the repository's packages/sdk-py until it is on PyPI (Python SDK).
Examples use real codes, NDCs and NPIs; responses are shortened, and the values you get are the current release's.

Ground rules for every recipe

Reference data, not advice. Nothing here is a coverage, credentialing, prior authorization, clinical or billing determination. Each recipe says what its answer is not; show that to your users with the answer.
No PHI. Send codes, NDCs, NPIs and payer ids, never anything about a patient.
Cite. Every response's meta names the source, the release (data_version) and the license; derived answers also carry derivation, confidence and evidence links (Responses).