SAAX Current Status

Last updated: 2026-10-24

Read this first

SAAX is experimental software. It records and verifies commitments for autonomous-agent work, with authorization, evidence, settlement, and recovery. Some parts are live today; the custody candidate is not a production service. Local tests are not an audit, and passing test counts are not a security guarantee. Nothing on this page is financial or investment advice.

What SAAX does

SAAX is a commitment protocol for autonomous commerce. It gives two parties - usually agents - a structured record of what was agreed, what was delivered, and what happens when something goes wrong. That record covers authorization (was the actor permitted to commit?), terms, acceptance criteria, evidence, outcome verification, settlement linkage, recovery, and finality. SAAX standardizes the record; it does not by itself guarantee that any payment is reversed or any dispute is resolved.

What is available today

  • Immediate payments - live on Base mainnet. The SAAX Router settles x402 and MPP payments with USDC on Base mainnet. This is non-custodial: no custody contract holds mainnet funds. Operated by the SAAX team. Service fees are disclosed in the 402 challenge before you pay.
  • Commitment creation via the create_commitment MCP tool and HTTP /route.
  • Receipt lookup by transaction hash at /receipt.
  • Conformance suite - published test vectors for the protocol specification.
  • MCP Registry listing for the SAAX MCP server.

What is locally demonstrated (not available to users)

  • Custody V3 candidate (SAAXEscrowCustodyV3.sol) - a locally tested candidate for escrow custody. Reported local tests cover settlement paths, Safe-based authorization, governance changes, time boundaries, and worker recovery.
  • Hosted testnet escrow flow (Custody V1) - an integrated escrow flow implemented and tested on Base Sepolia (chain 84532) with test USDC: signed agreements, EAS anchoring, escrow funding/release/refund/dispute, portable exports, and separate-process verification. An external-participant pilot package is prepared but not sent; no external participant has joined, and prior runs used operator-controlled test wallets.
  • Recovery has been demonstrated at specific crash boundaries; it is explicit and operator-assisted, not automatic.

What is being prepared or reviewed

  • An independent-review snapshot package has been prepared from committed repository evidence for the Custody V3 candidate. It pins the candidate source, harnesses, evidence, and supporting components with checksums.
  • The proposed review snapshot has not yet received owner approval; it is marked PROPOSED, NOT FROZEN. Nothing has been frozen, tagged, deployed, or released for review.
  • Independent security review has not been completed. The project owner is seeking a suitable review firm; no engagement or endorsement may be implied. No external reviewer has been engaged as of this update.

What remains before production custody

  • Deployment-target compatibility - not established; the candidate has run only on a local EVM (chain 31337). Local Cancun execution does not establish compatibility with a public target chain.
  • Production signing / governance - production signer provisioning and Safe governance wiring on a real deployment are not in place.
  • Operational limits - exposure caps, operating/recovery/canary parameters, and legal review are owner decisions, not production-set.
  • Public anchor finality - local EAS anchors are not public-chain finality; no public anchor finality is established.
  • Deployment / funding approvals - not authorized.
  • Independent security review and remediation, with reviewer re-verification, remain to be completed.

What a local test does and does not mean

A locally passing test battery demonstrates that the candidate behaves as its harness expects on a local EVM with synthetic keys. It does not mean the code is audited, secure, or ready for production or mainnet use. Local confirmations and local EAS anchors are not public-chain finality. Test counts are not independent security assurance. Production custody is not established until deployment compatibility, production signing and governance, operational limits, public anchor finality, and deployment/funding approvals are all in place and independently reviewed.

Where to learn more

SAAX Protocol is experimental software. Read the full terms of use before using it with real funds. Nothing on this page constitutes financial, legal, or investment advice.