Product

Developers

Free Tools

Now in early access

The knowledge layer that powers healthcare software

Every EHR, RCM platform, and AI billing company needs coding rules, payment calculations, and payer policies. Stop building your own rules engine. Call our API.

resolve billing context
curl -X POST https://api.rci.health/v1/knowledge/resolve
  -H "X-API-Key: YOUR_KEY"
  -d '{"ccn":"170001","cpt":"99213","payer":"Medicare"}'

One call. Six layers. The complete billing context.

Built for the companies building healthcare software

AI RCM platformsEHR & PM systemsClearinghousesDenial managementVoice AIBilling companies
6
knowledge layers resolved per call
3,400+
payer rule sets tracked
<50ms
median resolution latency
1,000
free API calls / month

One API. Every billing rule.

Replace your internal rules engine, fee schedule lookups, and scattered CMS data with a single API that resolves the complete billing context from a facility identifier.

L1–L6 knowledge resolution

// From a single CCN, resolve six layers:

CCN "170001"

L1 Location Kansas • GPCI values • MAC jurisdiction • Medicaid program

L2 Facility Short-term Hospital • MPFS payment system • CMS-1500

L3 Setting Outpatient • POS 22 • Facility rate • Modifiers

L4 Payer Medicare • 12-month filing • 5 appeal levels • Prior auth

L5 Service Group E/M rules • Documentation requirements

L6 Service 99213 • RVU 2.22 • GPCI-adjusted • $80.78

Knowledge Resolution

Full L1–L6 billing context from a CCN + CPT. GPCI values, payment system, billing form, payer rules, and expected payment in one call.

POST /v1/knowledge/resolve

Payment Calculation

Expected Medicare reimbursement using MPFS methodology. RVU components, GPCI adjustments, and conversion factor — calculated, not guessed.

POST /v1/knowledge/payment-calc

AI Code Research

Describe a procedure in plain English — get the right CPT/HCPCS with modifiers, documentation requirements, and NCCI edit checks.

POST /v1/agents/code-research

Denial Resolution

Interpret CARC/RARC codes, get appeal strategies, required documentation, and payer-specific filing deadlines. AI-powered with audit trail.

POST /v1/agents/denial-resolution

Payer Rules

3,400+ payer rule sets. Timely filing limits, appeal deadlines, prior auth rules, and policy changes — structured and searchable via API.

GET /v1/knowledge/layers/{ccn}/l4

Medical Necessity

Validate procedures against NCD and LCD criteria before submission. Returns coverage assessment, supporting criteria, and documentation checklist.

POST /v1/agents/medical-necessity

Billing Guide

Facility-specific billing guidance. Correct form (CMS-1500 vs UB-04), TOB codes, revenue codes, modifier requirements, and exceptions.

POST /v1/knowledge/billing-guide

MCP Server

Connect AI agents directly to the knowledge layer. Claude, Cursor, and custom agents can call resolve, calculate, and research as tools.

mcp.rci.health/v1/mcp

Building it yourself

  • Parse CMS fee schedule files quarterly
  • Build internal rules engine from scattered sources
  • Maintain payer-specific filing and appeal logic
  • Hand-code CCN to facility type mapping
  • Stitch together GPCI, RVU, and conversion factor data
  • Hire domain experts to interpret billing rules

Using RCI

  • One API call returns complete billing context
  • CMS data updated as it changes — you stay current
  • 3,400+ payer rules structured and searchable
  • CCN → facility type → payment system → billing form
  • GPCI-adjusted payment calculation built in
  • AI agents for code research and denial resolution
Pre-Submission Enrichment

Before a claim is submitted, call RCI to validate the code, check modifiers, verify the billing form, and estimate payment. Prevent denials before they happen.

Your platform → RCI API → Submit claim

Post-Denial Resolution

After a denial comes back, call RCI to interpret the CARC/RARC codes, get an appeal strategy, and understand the root cause.

ERA received → RCI API → Appeal strategy

AI Agent Grounding

Connect your AI agents to RCI via MCP server or REST API. Ground billing decisions in authoritative knowledge instead of hallucinated rules.

AI agent → RCI MCP → Sourced answers

Who builds on RCI?

Every company that handles healthcare billing needs the same knowledge. RCI makes it a single API call instead of an internal engineering project.

Built for healthcare

Healthcare billing data demands the highest standards. RCI is designed for security, reliability, and compliance from the ground up.

Security & Compliance

  • HIPAA compliant infrastructure
  • Multi-tenant data isolation
  • API key authentication on every request
  • Full audit logging
  • SOC 2 Type II (in progress)

Reliability & Scale

  • Cloud-native architecture
  • Rate limiting and abuse protection
  • Real-time monitoring and alerting
  • CMS data updated as it changes
  • Dedicated support for enterprise

HIPAA

Compliant

SOC 2

In progress

99.9%

Uptime target

<10 min

Support response

Stop building billing rules engines.

Get your API key, make your first call, and resolve the complete billing context for any facility in under 5 minutes. Free to start. Pay as you scale.

1,000 API calls/month free. No credit card required.