Skip to main content
Get a key first (getting started). Then match prefix → host. Paths are identical (/v1/policies, /v1/policy/parse, /v1/knowledge/resolve, /v1/mcp). The header is always X-API-Key — not a Bearer token. Playground + API Reference + a kp_test_ key are how you see what exists and what a call returns (sample inventory). Posted payers: GET /v1/policies. Your PDFs: POST /v1/policy/parse → /structure → /retrieve — Your policy documents. Do not send PHI on a test key.

​
How to get a key

  1. Sign in with a verified email.
  2. Sign up to mint a free key, or open the playground (key stays on the server).
  3. Admins and developers can also mint from console → API keys.
The full key is shown once. Use it only on https://sandbox.rcintell.com.
  1. Upgrade to an API plan.
  2. In console → API keys, create a live key.
  3. The console prints a curl against https://api.rcintell.com. Use that host only.

​
Hosts

API Reference has a server dropdown for these two URLs. A test key on production (or a live key on sandbox) returns 403, not production data.

​
Sandbox

​
Production

Same path. Different host and key.

​
MCP

Production MCP: https://api.rcintell.com/v1/mcp with kp_live_…. Full client snippets: MCP installation. The playground never puts a live key in the browser. It mints a kp_test_ key server-side.