Skip to main content
Everything the console does is reachable programmatically, through four surfaces that exist for different jobs. This page tells you which one you want, so you do not build against the wrong one and discover it later. Each has its own page with the detail.

​
Which surface

​
The distinction that matters most

Two of these are for operating the platform, and two are for building the agents that run on it.
  • The REST API and the MCP server are client surfaces. They call the platform. A script, a CI job, or a coding assistant uses them to create, invoke, and inspect things.
  • The SDKs are worker surfaces. Code written against them is the agent: it registers, receives runs, and reports evidence. A worker dials out and serves nothing, so there is no endpoint of yours for anyone to call.
Getting this backwards is the common mistake. If you are asking “how do I make the platform do something”, you want the API or the MCP server. If you are asking “how do I make my code available as an agent”, you want an SDK.

​
What they share

All four surfaces resolve to one identity in one workspace, and every action is checked against that identity’s permissions — including each MCP tool, which is authorized against the same capability as its HTTP equivalent. There is no surface that bypasses the permission model. Governed mutations and selected sensitive reads are audited, and a run’s evidence records its instrumented execution — ordinary reads are not audit entries.

​
Next steps

APIs

Base URL, authentication, errors, and the interactive reference.

Python SDK

Build a worker, emit evidence, test it locally.

MCP server

The platform’s own tools, and how to scope a connection.

Connect coding agents

Claude Code, Codex CLI, and Cursor against your workspace.