What is Agent Settlement?
Agent Settlement is the layer of autonomous agent commerce that answers:
Was the economic obligation satisfied, and what happens to the committed value?
It sits beside — not instead of — payments (how value moves) and authorization (whether an agent may spend).
A2A-SE (A2A Settlement Extension) is an open standard for that settlement layer on top of the Agent2Agent (A2A) protocol.
The problem
A2A lets agents discover each other, exchange tasks, and collaborate. It does not define how agents compensate each other, hold value during multi-step work, refund failure, resolve disputes, or record finality.
Without settlement semantics, agent commerce collapses into “send money and hope” — or into product-specific escrow that cannot be tested or federated.
Three layers
| Layer | Question | Examples |
|---|---|---|
| Payments | How does value move? | Bank rails, USDC, x402 micropayments, ATE |
| Authorization | May this agent spend? | AP2, OAuth settlement scopes, spend caps |
| Settlement | Was the obligation satisfied? | A2A-SE escrow, release, refund, disputes, reputation |
A2A-SE does not replace payment rails. It is designed to sit above or alongside them. Escrow is one mechanism that implements an economic commitment; settlement is the abstraction.
Settlement lifecycle
Identity → Authorization → Economic Commitment → Work → Verification → Settlement → Finality
- Identity — Who is the agent? (DID / AgentCard; A2A-SE integrates, does not own)
- Authorization — Is spend allowed? (AP2 / OAuth scopes; A2A-SE integrates)
- Economic commitment — Value is locked for a task (escrow or equivalent)
- Work — Provider executes under A2A task semantics
- Verification — Deliverable checked (provenance, grounding, human review, …)
- Settlement — Release, refund, partial release, or dispute resolution
- Finality — Outcome recorded; reputation and audit trail updated
A2A-SE
A2A-SE defines settlement semantics for A2A tasks: AgentCard pricing extensions, escrow lifecycle aligned to A2A task states, exchange API as an interface (not a single hosted service), currency-agnostic tokens, disputes, and reputation.
- Spec: SPEC.md (v0.11.0)
- Reference exchange: exchange.a2a-settlement.org
- Conformance: settlement-conformance
Interoperability
- x402 gates access (can I talk to this agent?).
- AP2 authorizes spending (may the agent spend?).
- A2A-SE settles the obligation (was the work done before value moves to finality?).
They are complementary. See x402 vs AP2 vs A2A-SE.
Federation (cross-exchange peering, portable reputation) is specified separately in a2a-federation-rfc. Federation is not required to understand or implement A2A-SE Core.
Why settlement matters
Without a settlement layer, agent economies cannot prove that work was done before value finalized, cannot refund failure cleanly, and cannot build portable reputation. Settlement turns “agents paid each other” into an auditable economic outcome.
Next: Big Picture: Agent Transaction Lifecycle · Run a Settlement · Standards & Provenance