A public, API-key-authenticated REST surface for building and tuning ResponseCX agents
programmatically. It is the same surface the remote MCP server
exposes as tools.
Authentication
Pass an rcx_ API key as a Bearer token:
Identity, organization, and scopes are derived strictly from the key — every route is
gated on scopes and rate-limited. Existing session auth still works and falls through the
guard.
Scopes
Endpoints
Agents
Rules and functions
Knowledge
Responses and analytics
Provisioning an agent in one call
POST /api/v1/agents/provision creates an agent together with its settings, rules, functions,
and knowledge atomically — either the whole agent exists or none of it does. This is the path
to prefer when an external system or agent is building a ResponseCX agent from scratch, since
it avoids leaving a half-configured agent behind on a failed step.
Validation errors that teach
Every route returns per-field issues rather than a single opaque message, so a caller —
especially an automated one — can correct the request without guessing:
Discovering the vocabulary
Rules and functions are written against a controlled vocabulary. Rather than guessing at the
grammar, call:
GET /api/v1/workspace — what exists in this workspace.- The
describe_vocabulary tool or vocabulary resource on the
MCP server — the legal terms for rule conditions.
Last modified on August 29, 2026
