Skip to content

Developers

Build against the control layer

Review the documented identity, permission and authorization sequence for your external agent.

Read the quickstartRead API reference

Interfaces

Integrate the same control model

  • APIRegister identity, define permission, request authorization, and inspect decisions and approvals, each recorded separately.
  • SDKA convenience layer over the same contract; the server still enforces every check. Internal, not yet published.
  • MCPAn interface to the same financial controls, not a separate authority.

One control core

The same checks, whichever interface sends the request

  1. Agent identity
  2. Permission and limits
  3. Policy
  4. Human approval when required
  5. Authorization

Sequence

The integration sequence

Each step is a separate record. Pairing grants no spending authority, and authorization is not execution.

  1. 01IdentityRegister the agent and its external agent identity in this workspace and environment.
  2. 02VerificationYour integration proves it holds its key by signing a challenge.
  3. 03PermissionSet a ceiling and an approval threshold, separate from credentials.
  4. 04PairingYour integration redeems a single-use pairing code with a proof and receives its credential.
  5. 05AuthorizationEach request receives ALLOW, DENY or APPROVAL_REQUIRED.
  6. 06ExecutionNot available yet. An authorized request is not sent anywhere.

Start with the quickstart.

Register an identity, verify it, set a permission and request authorization in a test workspace.

Read the quickstartGet started