Signed Medicare answers as agent tools.
Ask an AI agent what Medicare's sources state for one DME claim line, and get a cited, as-of answer with a receipt: provider standing, the fee, the coding edits, and the documentation requirements in force on the date of service. The same signed answer behind the API and the SDK, exposed as MCP tools your agent calls directly. Verzi does not decide whether a claim is supported, covered, or paid.
Endpoint https://mcp.verzi.health/mcp · Streamable HTTP · auth Authorization: Bearer or X-API-Key
Support: [email protected].
What it is
Three doors to one room. MCP is the agent door.
The /v1 API is the single source of truth. The MCP server is derived from it, never hand-maintained in parallel. An MCP call is an API call through a different door. The answer is the same signed answer: the fact, its source, the version in force, and a hash you can replay. Built for RCM and medical-coding engineers and AI-agent builders.
The signed answer
One claim line, four blocks, each with its own receipt.
For one HCPCS code, provider, payer, and date of service, the signed-answer tool returns one block per question. Each block carries its own fact and its own receipt: the version id, the source file id, and the sha256 you can replay. When a source does not cover the line, the block returns an honest gap, not a guess. There is no cross-check boolean, the chart is the customer's layer.
Codes and amounts only. The signed answer serves HCPCS codes and dollar amounts, never a CPT descriptor. Medicare DME today. All of Medicare and Medicaid next.
Tools
Six tools. Keyless, free, and paid.
A keyless tool needs no key. A free tool needs a key. A paid tool needs a key and the signed-answer entitlement, and it is hidden from an unentitled agent's tool list.
Connect
Add the server to your agent.
The server speaks Streamable HTTP at https://mcp.verzi.health/mcp. Send your Verzi API key as Authorization: Bearer, or in the X-API-Key header. Keyless tools answer without a key; the free and paid tools read the key. Support is [email protected].
# add the remote server with your key claude mcp add --transport http verzi \ https://mcp.verzi.health/mcp \ --header "Authorization: Bearer vh_live_…"
{
"mcpServers": {
"verzi": {
"url": "https://mcp.verzi.health/mcp",
"headers": { "Authorization": "Bearer vh_live_…" }
}
}
}
Then ask in plain language. "What did Medicare require for E0601 for this NPI on 2024-01-15 in UT?" The agent calls the signed-answer tool, and returns the four blocks with their receipts. Full tool and parameter reference lives in the docs.
Pricing
Free current-state. Paid signed answer.
A free key covers the source archive and the catalog. Signed answers and the full CMS text are a paid plan, granted per account during the private beta. The first 3 design partners get 90% off for 12 months, then the regular price. Contact us for access and pricing.
Current-state tools
Explore the data and the provenance with no key, or a free-tier key.
- server_info and list_data_sources · no key
- The source catalog, license, cadence, and accuracy class
The signed answer
The cited, as-of answer with a receipt you can replay against the source bytes.
- The signed answer: four blocks, each with its receipt
- Changes: did policy move since the date of service
- The as-of version in force, and the sha256 to replay
Give your agent a signed answer.
Get a key, connect the server, and ask your first claim question in minutes.
Rules data, not PHI. Nothing Verzi serves contains patient information.