Integration reference
Reference for Standard’s Control transaction, CLI, MCP transport, application bindings, participant custody, and execution evidence.
Start with the interface you use. MCP, the SDK and the CLI are entry points to the same Control transaction: they share Standard’s account, permission and verification model. Connecting through any of them identifies the caller; it grants no access to another participant’s assets, and each operation still needs every required owner’s authority.
| Your goal | Start here |
|---|---|
| Connect an existing agent | Connect through MCP |
| Use Standard from an application | Application integration |
| Run or inspect work from a terminal | CLI guide |
| Understand the transaction and its contracts | Protocol reference |
Connect through MCP
An agent in an MCP-compatible client discovers the tasks available to its account, submits operation requests and receives verified results. The remote endpoint is https://standardruntime.com/api/mcp (Streamable HTTP), and connecting requires OAuth authorization of your account. MCP does not give Standard custody of the agent’s files. See Connect.
Application integration
The Node.js and browser application bindings let an application submit operation requests and receive verified results from its own code. Verification runs inside the SDK, in your environment, before your code receives the result.
CLI guide
The CLI sets up encrypted storage, key access and permissions, and submits tasks from terminals and scripts. Use it for participant-side preparation and review workflows.
Protocol reference
Every entry point carries the same transaction underneath: an operation request checked against the accepted profile, owners’ permissions, and account limits; protected execution; and a result with evidence the receiving client verifies.
Private inputs never travel through MCP or any other entry point. Entry points carry encrypted-input references, and the confidential runtime retrieves the inputs from the owners' storage.
Always use the tools, methods and schemas your authenticated account actually exposes. Do not invent task names, fields or capabilities.
Operation requests
An operation request describes one task under an accepted operation profile. It contains:
| Part | Contents |
|---|---|
| Profile and Space revision | The exact accepted profile and Space governance revision for this operation. |
| Code or model | A reference to the approved code or model and its exact digest. |