At a glance
The web console
Everything KAOP does is available in the console: building and deploying agents, reading runs and their evidence, operating modules, connecting integrations, and managing identity and access. It is served as its own application and talks only to the control plane, so console and backend releases are independent.The REST API
The primary programmatic surface, under/api/v1. Anything the console does is available here —
agents, runs, chat, triggers, schedules, webhooks, workflows, integrations, credentials, and
evidence.
/api/docs on your workspace host. See
APIs.
Requests authenticate with a token and receive a JSON
401 when unauthenticated. Browser sessions
use SSO instead — see Signing in.The SDKs
An agent’s behavior lives in a worker you write and run. The SDK handles the protocol — registration, receiving work, and streaming evidence back — so your code can be about the agent.Python SDK
komodor-agentops. The primary authoring path, whatever agent framework you build on.Go SDK
A native Go worker SDK for teams who would rather not ship a Python runtime.
MCP: two different things
Both use the Model Context Protocol, and they point in opposite directions — worth keeping straight.
Coding assistants connect over the MCP server: Claude Code, Cursor, and Codex can query your
workspace and invoke agents from your editor. See
Connect coding agents.
Slack
Connect Slack and people invoke agents from a channel and get results in the thread. Routing rules decide what each inbound message does — an agent, a workflow, or an incident pipeline can be the target. See Channels.Agent-to-agent invocation
Agents can invoke other agents through the control plane, which keeps the call authorized and recorded like any other run rather than becoming an unobserved side channel. See Orchestration.Next steps
Architecture
How these surfaces sit around the control plane.
Developer tools
The programmatic surfaces in depth.