API reference (RC-API)

This describes the contract operators rely on. Exact payloads evolve—always check server.ts / route modules in RC-API for the live list.

Unauthenticated / public

• GET /health — liveness for tray and ops.

Authenticated (Bearer RC_API_KEY)

Typical patterns (names as in reference tree):

• GET /tools/list-all — full catalog + metadata used by MCP to build subcommand list.
• GET /tools/docs — aggregated docs where enabled.
• POST /tools/execute — primary workflow executor for execution_target: remote tools (body includes tool name + parameters per handler).

Rules / constitution fragments

Used by tray + MCP constitution assembly, e.g.:

• GET /rules/base
• GET /rules/tool_policy/:id
• GET /rules/behavior_profile/:id
• GET /rules/prompt_policy/:id
• GET /rules/latest (and related—see RC-API routes)

Files / uploads (when deployed)

• Upload helpers for large payloads (e.g. Gemini file flows)—see RC-API /files/... routes if present.

Deprecated mental model

Do not assume dozens of legacy per-tool POST routes (e.g. /analyze-sentiment) as the primary surface—modern path is /tools/execute + MDC workflows.

Related

• architecture.md
• configuration.md