SAAX components vary in maturity — live mainnet payments are public beta, escrow custody is testnet-only preview. Use at your own risk. Real funds are processed on Base mainnet. Test with small amounts. No warranty, no recovery guarantee, no liability. Full terms

Durable Commitments for Agentic Commerce.

SAAX Protocol - Solvent Applied Autonomous Exchange Protocol

SAAX provides a verifiable commitment lifecycle for agentic commerce transactions, connecting agreements, payment evidence, fulfillment, and recovery. As AI agents increasingly authorize payments, coordinate purchases, and execute commercial tasks, SAAX provides a durable record of what was agreed, what occurred, and what remains unresolved.

Immediate payments: Public beta · Base mainnet Specification: Public · versioned v1.0.3 Signed Discovery & acceptance: Beta Custody finance: Testnet preview · Base Sepolia Unreleased custody: Development / security review MCP Registry: Listed

Public signed Discovery, free preflight and onboarded-buyer acceptance create commitments without moving funds. The complete custody integration has real Base Sepolia release/refund evidence, but remains operator-run testnet preview, not a public financial API. Mainnet is limited to existing immediate x402 payments. No mainnet custody or completed independent audit.

SAAX Protocol — Public Beta. Immediate-payment functionality is available on Base mainnet; escrow custody remains limited to testnet. Independent external security review is pending. Live transactions involve financial and technical risks, including potential loss of funds and irreversible blockchain transfers. This notice does not constitute a guarantee of reimbursement, dispute recovery, or financial protection.

The Problem SAAX Solves

A payment record does not describe every obligation. SAAX gives existing transactions a structured commitment record; it does not generate demand or guarantee safe automation.

The buyer problem

When you pay an agent to do work, there's no record of what you agreed to. If the output is wrong, there's no way to prove it. If the agent retries, you might get charged twice.

The seller problem

When an agent does work for a buyer, there's no structured record of what was agreed or what was delivered. If the buyer disputes the charge, there's nothing to resolve it with.

What SAAX adds

A commitment record that binds the terms, the evidence of fulfillment, and the recovery policy before execution begins. Both sides work from the same record.

Who This Is For

SAAX is for:

  • Developers integrating agent services into products who need a verifiable record of what was purchased
  • Buyers paying agents for work who want structured evidence of fulfillment
  • Sellers operating agent services who want a defensible record when disputes arise

SAAX is not:

  • A marketplace. It does not generate demand or guarantee transaction outcomes.
  • A payment rail. It sits above the rail and records what the payment was for.
  • A source of guaranteed customers. Signed capability discovery checks compatibility; it does not create demand or establish service quality.

What the Protocol Defines

SAAX is not a payment rail, an identity system, or a marketplace. It is a standard for what a commitment means — what must be true for it to be valid, fulfilled, and final.

AuthorityProof that an autonomous actor was authorized to enter the commitment.
TermsWhat was promised, at what price, under what constraints and deadlines.
Acceptance criteriaWhat objectively constitutes successful fulfillment.
EvidenceWhat external, independently-verifiable proof is required.
Outcome verificationHow evidence is evaluated against the criteria.
RecoveryWhat happens on failure, timeout, partial completion, or dispute.
Settlement linkageHow an external economic settlement relates to the commitment.
FinalityWhen the commitment conclusively reaches its terminal state.
AuditWhether another party can reconstruct the full history.
Commitment IDThe persistent reference that binds the commitment record to the settlement, across any rail. Carried in the rail's external-reference field at payment time; the on-chain transaction reference is recorded on the commitment at settlement; the receipt resolves by transaction hash back to the commitment ID.

The Commitment Lifecycle

A SAAX commitment is a vendor-neutral record that moves through a defined sequence — from authorization to finality. It is independent of any single payment rail, identity system, or marketplace.

1. Authorization 2. Agreement 3. Execution 4. Fulfillment evidence 5. Outcome verification 6. Settlement or recovery 7. Finality 8. Audit

Authorization proves the actor was permitted to commit. The agreement records terms and acceptance criteria before value moves. Evidence is verified against those criteria. Settlement links the external payment to the commitment, and recovery defines what happens on failure or dispute. The commitment is portable — it survives beyond the worker or platform that executed it.

For Developers

Read the Protocol Versioned public specification

The full commitment lifecycle specification — authority proofs, evidence abstraction, verification policies, recovery semantics, settlement linkage.

Read the Protocol →

Try SAAX Router Public beta

Connect through https://www.saax-protocol.com/mcp or the site HTTP interfaces. Existing immediate payments settle USDC on Base mainnet via x402. The signed prepare_commitment and accept_commitment path is separate from the older create_commitment tool and creates no payment or service execution.

Try SAAX Router →

Run Conformance Tests Live

Conformance fixtures and a test runner for validating SAAX implementations against the specification.

Run Conformance Tests →

Verify Discovery before spending Beta

Authenticate the provider key independently, verify a free signed proposal, then accept with an onboarded buyer key. Consent binds exact terms; it is not a payment authorization or custody verdict.

Start without moving funds →

Resolve a Commitment by Transaction Hash

The receipt endpoint resolves a settled transaction back to its SAAX commitment ID. Query https://saax-protocol.com/receipt?txHash=<hash>&rail=x402 with any settled x402 transaction. It returns the commitment ID, the rail, the payer, the payee, and the settlement timestamp. The payer is the buyer record (an email address where one was recorded) and the payee is the seller identifier from the terms — either can be null in a minimal record. A receipt confirms a settlement reference; it does not by itself prove the work was fulfilled or independently verify the lifecycle. The live receipt lookup is operational; see current status for the verified boundaries.

Deploy a Node Coming Soon

Node deployment guidance and network participation documentation.

Coming Soon

What you need

  • EVM wallet on Base
  • USDC on Base mainnet (immediate x402 payments)
  • No ETH required for the x402 payment itself

Testnet escrow flows are separate: they run on Base Sepolia and need testnet USDC plus testnet ETH for gas, and the custody contract must be funded. Service fees are shown in the 402 challenge before you pay.

Current Status

Last verified: 2026-11-06. Component maturity varies; the table below states each component's current status. The surfaces are not interchangeable.

ComponentStatusNotes
Protocol specificationPublic specification — versionedv1.0.3; see spec
Routing & immediate paymentsPublic betax402 via USDC on Base mainnet; operated by SAAX team
Signed Discovery / acceptanceBetaPublic signed profile, free preflight and configured-buyer commitment creation; no financial side effects
Commitment verification & receiptsBetareceipt lookup at /receipt (verified live 2026-11-06; see status); MCP verification unaffected
Escrow custody (V1)Testnet preview — not approved for mainnet fundsBase Sepolia only; test assets; no mainnet custody
Custody V3 candidate; governance candidatesUnder development / security reviewlocal EVM only; review owner-approved snapshot for independent review, review not completed; no completed independent audit

Live on Base mainnet

  • Immediate payments via the SAAX Router — x402, USDC on Base. Operated by the SAAX team.
  • Commitment creation via the create_commitment MCP tool and HTTP /route.
  • Receipt lookup by transaction hash at /receipt.
  • Not escrow-backed. No custody contract holds mainnet funds.

Connected custody flow: testnet preview

  • A separately signed Sepolia profile and buyer-authorized financial agreement connect to actual Custody V1 funding, release and refund on Base Sepolia (chain 84532), test USDC only.
  • Complete independent export verification passed without application database access. The defined self-test uses deterministic SHA-256 evidence; financial execution is not a public API.
  • An external-participant pilot package has been prepared but not sent; no external participant has joined. Prior testnet runs used operator-controlled test wallets.
  • Recovery has been demonstrated at specific boundaries; it is explicit and operator-assisted, not automatic.
  • This flow does not use the local Custody V3 candidate.

Custody V3 candidate: locally tested, review preparation in progress

  • The Custody V3 candidate (SAAXEscrowCustodyV3.sol) has been tested only on a local EVM (chain 31337) with synthetic test keys. Reported local coverage includes settlement paths, Safe-based authorization, governance changes, time boundaries, and worker recovery.
  • An independent-review snapshot package has been prepared from committed repository evidence and owner-approved as the baseline for independent review (manifest SHA-256 920ddff8…). Independent review has not been completed; approval-for-review is not an audit, not production readiness, and not deployment approval.
  • No independent security review has been completed. The project owner is seeking a suitable review firm; no engagement or endorsement is implied.
  • Production custody is not established. Deployment compatibility, production signing/governance, operational limits, public anchor finality, and deployment/funding approvals remain open.
  • Local tests and local anchors are not public-chain finality, and passing test counts are not an independent security assurance.

Read the full current status →

All roles in the testnet self-test are operator-controlled. A local chain named 84532 is not public-testnet proof; the fresh records have public-chain successful receipts, decoded calls/events and historical token/state checks. Disputed V1 funds can remain frozen if the evaluator disappears. Internal tests are not an independent audit. Read the technical walkthrough →

Live on Base Mainnet — Immediate Payment

A real Base mainnet x402 immediate payment, verified end to end. This demonstrates the payment path, not escrow.

Commitment IDsaax_1e904a1582abc99b
Base mainnet txHash0x7ac2efe8c440762c21aacab2d8fc055b0195a3685b6c8a6ab475077fc4b94e75
Basescanhttps://basescan.org/tx/0x7ac2efe8c440762c21aacab2d8fc055b0195a3685b6c8a6ab475077fc4b94e75
Receipt URLhttps://saax-protocol.com/receipt?txHash=0x7ac2efe8c440762c21aacab2d8fc055b0195a3685b6c8a6ab475077fc4b94e75&rail=x402
Amount0.05 USDC
Railx402

The commitment was created via the create_commitment MCP tool. The x402 payment carried the commitment ID in the extensions field. Settlement broadcast on Base mainnet. The receipt endpoint resolves the real txHash back to the commitment ID.

This example was executed from an operator-controlled wallet. It demonstrates the immediate-payment path and the receipt linkage end to end. It is not an escrow demonstration and not external-user validation.

Query the receipt endpoint →

Agentic Commerce Technical Articles

A primary-source map of the agentic-commerce protocol ecosystem, and how a durable commitment layer fits around it.

Agentic Commerce Protocols in November 2026

ACP, AP2, UCP, x402, MCP, A2A — what each officially covers, what its own docs exclude, and where a commitment layer fits.

What Happens After an AI Agent Pays?

x402 and stablecoin settlement prove value moved, not delivery. Durable idempotency and reconcile-before-respond make agent payments recoverable.

Google AP2 and SAAX

Authorization evidence vs durable commitments — how the mandate layer and the commitment layer complement each other.

MCP, A2A, UCP, and SAAX

A reference architecture for reliable agent commerce — what is implemented today and what is illustrative.

For Suppliers

Want your agent discoverable through SAAX? The Router reads the ERC-8004 Identity Registry on Base: registering your agent there with its capabilities and an endpoint is the path to being found by SAAX routing. Registry integration is implemented in the Router; the searchable supplier pool is still small and early.

ERC-8004 Identity Registry documentation →

SAAX Premium

Premium access to the trust and enforcement layer of the protocol. Cancel anytime.

Subscriptions are managed through Stripe. Access is tied to the email address on the subscription record; the email key does not by itself prove identity. Plan entitlements apply to the SAAX Router and premium features as they ship — features listed as part of a plan are not all available today, and SAAX does not guarantee any particular outcome, SLAs, or compliance status.

14-Day Free Trial

$0/14 days

Full access to SAAX Premium for 14 days. No charge until the trial ends. Cancel anytime.

  • Everything in Premium
  • Card required at signup
  • Cancel before the trial ends to avoid being charged

Start Free Trial →

Developer

$29/month

For individual agent builders and solo operators.

  • Evidence verification for high-value commitments
  • Standard supplier reputation data
  • Standard routing
  • Community support

Subscribe →

Business

$199/month

For small teams and early-stage agent startups.

  • Everything in Developer
  • Authority proof validation
  • Enhanced supplier reputation data
  • Priority routing in the SAAX Router
  • Extended audit access
  • Email support

Subscribe →

Enterprise

Custom pricing

For regulated industries and large agent fleets.

  • Everything in Business
  • Custom verification limits
  • Compliance workflows
  • Dedicated support
  • Custom SLAs
  • Audit exports

Contact us →

Before You Use SAAX

What SAAX Does Not Guarantee

SAAX standardizes recovery and dispute states within the commitment lifecycle. Enforcement mechanisms are in development. SAAX does not guarantee reimbursement, reversal, or resolution of disputes. Enforcement depends on the parties involved and any arbitration mechanisms they agree to.

  • No warranty
  • Real funds on Base mainnet
  • No recovery guarantee
  • Your keys, your responsibility
  • No endorsement of suppliers
  • Component maturity varies — see the current status

Read the full terms of use →