Every policy capability is available three ways — in the UI, over a REST API, and to AI agents over MCP. The policy surfaces are login-gated and metered; sign in to use them.
Hybrid semantic + keyword search over payer medical-policy and reimbursement documents, with the extracted billing rules.
GET /api/v1/lookup/?topic=&payer=lookup, fetch_documentpolicy.lookup / policy.documentHow a payer's policies changed over time — dated changes for a brand family, filterable by state and date.
GET /api/v1/policies/?payer_id=&state=policy_changespolicy.changesResolve partial card-style fields (company, plan, EDI payer id, NAIC, BlueCard prefix — never a full member id) to the true top-level payer.
POST /api/v1/payers/resolve-cardresolve_payerpolicy.resolve_payerWhich policies govern a payer (+ optional state / line of business / procedure code) — authority set + deterministic narrowing with a typed basis.
GET /api/v1/payers/applicable-policiesapplicable_policiespolicy.applicabilityThe health and last-checked freshness of every source we monitor (read-only mirror of our surveillance).
GET /api/v1/sources/stale— (UI: /policy/monitoring)policy.monitorThe Payer-Policy MCP server exposes 7 tools. Set up the MCP connection →
lookup — Search payer medical/billing policy DOCUMENTS by a clinical or billing topic (hybrid semantic + keyword). Optionally scope to one payer. Returns documents with snippets and their extracted billing rules.fetch_document — Fetch HANK's stored copy of a policy document — the full scraped policy text plus extracted billing rules — by source_id from a lookup result (no need to re-fetch the payer's bot-walled site).payer_suggest — Resolve a partial payer name to candidate payers ({id, name}) — use to find the exact payer string to pass to lookup's `payer` argument.topic_suggest — Suggest clinical/billing TOPICS that HANK actually has indexed policy documents for (grounded, never invents a topic). Discover what you can ask lookup about, or disambiguate a vague topic. Paged via an opaque cursor.policy_changes — Policy CHANGE history for a payer (brand family): dated rows of detected changes (effective date, type, severity, summary), optionally since a date. Answers 'how has <payer>'s policy changed over time'. Paged via an opaque cursor. Metered.resolve_payer — Resolve partial insurance-identity FIELDS (company, plan, EDI payer id, NAIC, phone, state, BlueCard prefix — never a full member id) to the true top-level payer + corporate chain + applicable policies + PT-rate link. The RCM 'find my payer' use case. Metered.applicable_policies — Which policies APPLY to a payer (+ optional state / line_of_business / procedure code): the authority set (CMS/MAC inheritance) narrowed deterministically, each with a typed basis + rationale. confirmed_by='deterministic' if the LLM was unreachable. Paged via an opaque cursor. Metered.