Seal the runtime
The sealed-agent design extends the private inference boundary to model state, memory and execution policy. A measured image defines what code is trusted inside that boundary.
Enforce a mandate
Agents transact within defined spending mandates. A prefunded or collateralized lane specifies how usage is funded; on-chain enforcement rejects requests that breach the mandate.
In the product preview, create an agent and set an illustrative USDC limit. Select that agent during inference to test an accepted or rejected request.
Settle private commerce
The payment path uses x402 or Nanopayments in USDC. Confidential transfer amounts are shielded, while payment addresses remain visible. A scoped view key enables authorized payment disclosure.
Progress through the roadmap
Sealed agents, mandates and confidential payments form the E2 roadmap stage. The interface is a demonstration of the planned controls, not a deployed agent service.