Product

Developers

Free Tools

All use cases
Integration Pattern

AI Agent Grounding

AI billing agents hallucinate rules, invent modifier logic, and confuse payment systems. RCI's MCP server and REST API give your agents an authoritative knowledge source for every billing decision.

For: AI RCM platforms, voice AI, coding assistants, chatbot builders

How it works

architecture flow
Your AI Agent (Claude, GPT, custom LLM)
  │
  ├─ User asks billing question or agent needs context
  │
  ├─ Agent calls RCI via MCP Server or REST API
  │   ├─ resolve_knowledge   → Full L1-L6 billing context
  │   ├─ calculate_payment   → GPCI-adjusted Medicare payment
  │   ├─ research_code       → CPT/HCPCS lookup with AI
  │   ├─ resolve_denial      → CARC/RARC interpretation
  │   ├─ search_payer        → Payer-specific rules
  │   └─ get_billing_guide   → Form, modifiers, TOB codes
  │
  ├─ Agent receives structured, sourced data
  │
  └─ Agent responds with accurate, grounded answer

Connect via MCP Server

Add the RCI MCP server to your agent's configuration. Works with Claude, Cursor, and any MCP-compatible agent.

MCP client config
{
  "mcpServers": {
    "rci-knowledge": {
      "type": "http",
      "url": "https://mcp.rci.health/v1/mcp",
      "headers": {
        "X-API-Key": "YOUR_KEY"
      }
    }
  }
}

Your agent now has access to 6 tools and 4 prompts for billing knowledge.

Or call the REST API directly

If your agent framework doesn't support MCP, call the same endpoints directly via HTTP.

python
import httpx

class RCITool:
    """Tool for LLM agents to query billing knowledge."""

    def __init__(self, api_key: str):
        self.client = httpx.AsyncClient(
            base_url="https://api.rci.health",
            headers={"X-API-Key": api_key},
        )

    async def resolve(self, ccn: str, cpt: str, payer: str = "Medicare"):
        """Resolve complete billing context for a facility + service."""
        resp = await self.client.post("/v1/knowledge/resolve", json={
            "ccn": ccn, "cpt": cpt, "payer": payer,
        })
        return resp.json()

    async def research_code(self, query: str, ccn: str = None):
        """AI-powered code research from natural language."""
        body = {"query": query}
        if ccn:
            body["ccn"] = ccn
        resp = await self.client.post("/v1/agents/code-research", json=body)
        return resp.json()  # Returns job_id, poll for result

    async def payment(self, ccn: str, cpt: str):
        """Calculate expected Medicare payment."""
        resp = await self.client.post(
            "/v1/knowledge/payment-calc",
            json={"ccn": ccn, "cpt": cpt},
        )
        return resp.json()

Tools available to your agent

resolve_knowledge

Full L1–L6 resolution. Returns GPCI, payment system, billing form, payer rules, RVUs, and payment estimate.

calculate_payment

MPFS-based payment with GPCI adjustments. Returns RVU component breakdown and estimated payment.

get_billing_guide

Billing form, TOB codes, modifier requirements, and consolidated billing rules.

research_code

AI-powered CPT/HCPCS/ICD-10 research. Submit natural language, get structured coding guidance.

resolve_denial

CARC/RARC interpretation with appeal strategies and payer-specific deadlines.

search_payer

Payer-specific rules: timely filing, appeal levels, prior auth requirements.

Why agents need live knowledge

Training data

  • • Fee schedules go stale (updated annually)
  • • Payer rules change quarterly
  • • NCCI edits update every quarter
  • • No facility-specific context
  • • Hallucinated modifier requirements

RCI knowledge layer

  • • CMS data updated as it changes
  • • Payer rules tracked in real time
  • • NCCI edits current to the quarter
  • • Facility-specific via CCN resolution
  • • Structured, sourced, audited responses

Ground your agents in real knowledge

Connect to the MCP server in under 2 minutes or call the REST API directly.