The problem
Agents can now act on behalf of people, including spending their money. The benefit is that agents can complete tasks end-to-end without ongoing oversight. Protocols such as AP2 and TAP help constrain what agents can do and spend with explicit mandates and instructions. Yet, as agents become more capable and users are exposed to opt-out features, accidental purchases (or actions) will take place.
If the agent completes a task in a way the user is not expecting, the usual recourse is a refund request or a chargeback after the order is already final. This could involve shipping items or disputing charges. Nothing in the transaction tells the merchant whether a person or an agent made it, so a merchant has no reason to treat agent purchases differently, and an agent has no reason to say what it is.
The idea
Give the person a window after a declared agent takes action to undo it. Rather than trying to prevent all unexpected actions (impossible), agents can be used to complete real tasks, but the task is not final until the window closes or the person confirms.
The prior art is a worktree: the work happens in a space that can be thrown away until someone accepts it.
In order to make this possible, the person authorizing action hears about it right away. The message says what was done, what it cost, and the deadline. A reply of ctrl-z revokes the action. Any other reply confirms it early.
Why the agent has to declare itself
The extended window is what an agent, and so the person responsible for the agent, earns by declaring. An undeclared agent looks like a person. In the case of a a purchase, an undeclared agent looks the same as a human and so an agent's purchase gets the merchant's ordinary terms. A declared agent tells the merchant that software is acting on a person's behalf, and that there is a person who can be reached and who can say yes or no. That gives the merchant a reason to hold the order open longer than usual. Declaring is how the revocation window becomes available, and the revocation window's benefit for both parties is the reason to declare.
Where it fits
Reversal works when the thing has not been used or delivered yet, and when the merchant can hold the order in the meantime.
| Category | Example | What holding the order means |
|---|---|---|
| Tickets | Concert seats | The seats are reserved for the buyer. A revoke releases them back to inventory. |
| Travel | A flight to Barcelona | The fare is held and the ticket is not issued until the window closes. |
| Goods that ship | A jacket, a record | The order is accepted and paid for but not handed to the carrier until the window closes. A revoke cancels before shipping. |
| Digital artifacts | A software license, an ebook | The download or key is withheld until the window closes. |
Where it does not fit
Some actions cannot be undone once taken. A sent message has been read. A flight already flown is gone. A ride, a meal, or any service already consumed cannot be handed back. A deleted record may not exist anywhere to restore. The revocation window does not cover these, and the idea is not meant to. Part of the work is deciding which actions get a window at all, and if there is a cost associated with offering the window in the first place.
The message flow
- Alert. The agent acts, and the person gets a message with what was done, the cost, and the deadline.
- Reply. The person answers inside the window.
- Outcome. One of three things happens:
- Revoked. The reply is
ctrl-z. The order is cancelled and the person gets "cancellation confirmed". - Confirmed early. The reply is anything else. The order becomes final and the person gets "purchase confirmed". The window closes early because the person chose to close it.
- Closed on expiry. There is no reply. In this model the order becomes final, because the purchase was already made. A person could choose the opposite default for large purchases, where silence revokes instead.
- Revoked. The reply is
What the illustration leaves out
- Who holds the escrow and enforces the window. The illustration shows only the operator's side, that is, the person behind the agent.
- How a reply is verified as coming from the person. This would require some form of proof of authorization to ensure that the reply is from the same person who issued the request and the same person that issued the request is also the same as the person responsible for the agent and funds.
- The window closing with no reply. Described above but not shown, some safeguards would need to be in place to ensure that agentic actions are not invoked by bad actors in windows where the responsible party is not able to respond. Accept if no reply would likely be opt-in rather than opt-out.
- Actions where reversal does not make sense. The premise is disclosure opens a window to reconcile mistakes. For transactions where revocation is not possible, how would declaration be incentivized, if at all?
Open questions
Who holds the escrow and enforces the window?
The merchant could hold the order pending. The payment layer could hold the funds, closer to a chargeback with a fast path. A neutral party could sit between the agent and the merchant. Each puts the trust somewhere different, and the page leaves the choice open on purpose.
How long should the window be for each category?
A concert ticket for next week and a flight a year out do not want the same window. The deadlines in the two threads differ for that reason, but nothing here says how they would be set or by whom.
Who bears the cost of a revoked order?
A revoked order ties up stock and may miss a resale. The merchant, the agent's operator, or the person could carry that cost, and the answer changes what a merchant is willing to offer.
How is abuse handled?
A person could use the item and then revoke. Holding delivery until the window closes limits this for goods and digital items. It does less for anything consumed on the spot.
Which actions are reversible at all, and who decides?
The merchant may know best what it can hold. The person may care about different things. A shared list of reversible categories would help, but someone has to keep it. May require a parity primitive to the Mandate on the seller side.
What does the window do to the merchant's stock, pricing, and delivery?
Holding orders open delays delivery and may delay revenue. A merchant might price the window in, or limit it to declared agents with good history.