Build with the knowledge layer
One API call resolves six layers of billing context. Get your free key, pick your language, and start resolving in under 5 minutes.
Beta access status
HTTPS + TLS verifiedThe API is in dev beta for evaluation. Generate a free read-only key and call the base URL below with an X-API-Key header.
Beta API base
https://api-dev.rcintell.comAuth header
X-API-Key: YOUR_KEYTry it
This is an animated sample. Use the live playground to call the real API.
curl -X POST https://api-dev.rcintell.com/v1/knowledge/resolve \
-H "X-API-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"ccn":"170001","cpt":"99213","payer":"Medicare"}'Response
Get started in three steps
Get your API key
Generate a free read-only key at /signup. Send it as the X-API-Key header on every request.
X-API-Key: YOUR_KEY
Resolve knowledge
Pass a CCN + CPT code. Get six layers of billing context in a single response.
POST /v1/knowledge/resolve
{"ccn":"170001","cpt":"99213"}Use the response
Payment estimates, billing forms, modifiers, payer rules — structured JSON ready for your app.
{"estimated_payment": 80.78,
"billing_form": "UB-04",
"payer_filing": "12 months"}Facilities (test data)
The by-CCN endpoints (/v1/knowledge/*, /v1/codes/{code}/payment) resolve against facilities registered to your tenant. Every key comes with two demo facilities pre-loaded, and you can register your own for testing.
Pre-loaded demo facilities
Ready to use immediately — the examples on this page use 170001.
170001 Sunflower Medical Group (KS) 280003 Bryan Medical Center (NE)
Register your own
POST a CCN + name; state, type, and payment system are parsed automatically. Trial keys can register up to 25 test facilities.
curl -X POST https://api-dev.rcintell.com/v1/facilities \
-H "X-API-Key: YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"ccn":"050001","name":"My Test Hospital"}'Pick your language
The API is plain REST + JSON, so any HTTP client works today. Typed SDKs are on the way.
cURL / HTTP
AvailableAny HTTP client + X-API-Key headerPython
Availablerequests / httpxTypeScript
Availablefetch / axiosNew API families now documented
Recent platform additions include prior auth workflows, OpenFDA NDC search, UMLS concepts, encounter checks, fee schedules, payer denial-code lookups, and MCP transport.
Prior Auth DecisioningCRD-style prior-auth determination and documentation support
Drug Reference SearchOpenFDA-backed NDC product search and lookup
Terminology NormalizationUMLS concept search and standardization
Fee Schedule IntelligenceOPPS, DMEPOS, and lab pricing lookup workflows
Denial Pattern InsightPayer + industry denial code context
Encounter Readiness CheckClaim pre-check and encounter validation
MCP Agent IntegrationStreamable MCP access for AI workflows
What you can build
Knowledge resolution, AI agents, NCCI edits, NPI search, payer intelligence, and admin operations.
Knowledge ResolutionFull L1–L6 billing context
Payment CalculationGPCI-adjusted payment intelligence
Billing GuidanceForm + modifier decision support
AI Code ResearchCPT/HCPCS research support
Denial ResolutionAppeal strategy support
Medical Necessity ReviewNCD/LCD validation support
NCCI Safety ChecksEdit and bundling validation
Provider DiscoveryProvider lookup and validation
Payer IntelligencePayer policy and filing rule search
MCP Server
Connect Claude, Cursor, or any MCP agent directly to billing knowledge with streamable HTTP transport and an expanded tool catalog.
Free trial keys
Self-serve keys are read-only and rate-limited for evaluation. Generate one in seconds and explore the full read API surface.
Documentation
Knowledge layers
L1–L6 resolution, billing guides, payment calc
AI Agents
Code research, medical necessity, denial resolution
NCCI & NPI
MUE/PTP edits, add-on codes, provider search
Authentication
API keys, scopes, rate limits
Integrations
EHR, clearinghouse, payer system guides
Payment Calculator
RVU × GPCI × CF reimbursement tool
Playground
Call live endpoints from the browser
Pricing
Workspace and API pricing