xMandate Documentation
The trust control plane for agentic execution.
xMandate provides the missing infrastructure layer for a world where agents act autonomously -making payments, invoking tools, delegating tasks, and executing workflows across organizational boundaries.
The core thesis is simple: every governed action should produce portable, cryptographic proof that can be independently verified by any downstream party, without trusting the executor.
The Problem
Agents are becoming first-class economic and operational actors. Protocols like x402 and MPP enable machine-native payments. MCP protocolizes tool access. A2A enables cross-agent delegation. Enterprise workflows increasingly involve autonomous execution.
But none of these answer the fundamental trust questions:
- What was allowed? -Was there a policy governing this action before it executed?
- What happened? -Is there a tamper-evident record of the action and its outcome?
- What can be verified? -Can a third party independently confirm the record without trusting the executor?
How xMandate Works
xMandate operates on a three-part model that applies at every execution boundary:
| Phase | What it does |
|---|---|
| Policy | Define constraints before execution -what agents are allowed to do, under what conditions, within what bounds. |
| Attestation | After execution, issue a signed Settlement Attestation Receipt (SAR) -a cryptographic, tamper-evident record of what happened and the verdict. |
| Verification | Any downstream party can independently verify the receipt -offline, without callback, without trusting the signer. |
What is a SAR?
A Settlement Attestation Receipt is the core primitive. It is a structured, Ed25519-signed record containing:
- What was checked -task identity, policy context
- What the verdict was -PASS, FAIL, or INDETERMINATE
- When it was issued -ISO 8601 timestamp
- Who signed it -verifier key identity
SARs are canonicalized using JCS (RFC 8785), hashed with SHA-256, and signed with Ed25519. Any party with the public key can verify a receipt independently.
Learn more: SAR Receipts | SAR SDK
The xMandate Stack
| Layer | Component | Status |
|---|---|---|
| OSS Foundation | xmandate-sar-formatter -TypeScript SAR signing and verification | Available on GitHub and npm |
| Control Plane | xMandate Control Plane — centralized policy management, receipt storage, verification services | Coming |
| Extensions | Verifier registry, policy registry, CI/API/MCP integrations | Planned |
Next Steps
Understand the attestation primitive -structure, signing, and verification.
Learn about SARs →