Agent Transaction Protocol

Undo for tools that were never meant to undo.

MCP 2026-07-28 tells an agent how to call a tool. It does not say what happens when step three fails after step one has already moved money. Reverta is the specification and the coordinator that sit in between.

Why agents need rollback Run the three-step demo Declare a compensatable tool

Three steps: a ledger transfer and a stock move apply, the carrier returns HTTP 500, and compensation restores the first two. The transaction ends ROLLED_BACK.
The demo plan. Step three fails, and the first two effects are undone in reverse.

Shadow first

Branchable tools mutate a private branch. API tools return a recorded dry-run example. Production state waits for the policy gate.

A person for the irreversible

Sending a wire or an email cannot be inverted. Those steps pause, persist, and resume hours later without holding a thread.

A hash for every hop

Each ledger entry links to the previous SHA-256. Replay walks that chain in a sandbox and refuses to call live endpoints.

Six lessons

01Why rollback is missing
What MCP standardizes, and the failure modes it leaves open.
02Run the demo
Ledger, stock, a carrier 500, and a reverse compensation you can see.
03Declare a tool
Reversibility, compensation expressions, and the signed manifest.
04Policy and approval
Blast radius, irreversible holds, and how to resume a parked transaction.
05Ledger, replay, chaos
The hash chain, sandbox replay, and the recovery CSV.
06Python, Java, and MCP
Three ways to point an agent at the proxy.