Your AI can send money now. That stopped being hypothetical today: an AI payments app launched publicly this morning, and its pitch is simple. Connect the AI you already use, set limits, and tell it to pay. Recipients do not even need an account; they get a link and cash out to their bank.
So here is the first question of the agent money era, and it is not "can my AI pay?" It is this: when your AI says it paid, what do you actually hold?
The dinner test
Run the launch demo forward one week. You tell your AI to pay Maya $24 for dinner. The AI replies: done. Maya says nothing arrived. Now what?
I read the new app's own public documentation this morning, the pages that explain how an assistant connects and what it may do. Here is what you hold in that dispute, based on those pages:
- An activity list inside the same company's app. It shows your payments and where each stands, and it is the company's own record, on the company's servers, behind your account login. Maya cannot open it. Neither can anyone else you might ask to arbitrate.
- A status check the assistant can run against the same system. Same source, same problem: the answer comes from the party whose record is in dispute.
- A duplicate guard with a short memory. Per the docs, each payment carries a key the assistant makes up, so the same call repeated within 10 minutes returns the first result instead of paying again. Ten minutes. After that window, the guard the docs describe is gone.
None of this makes the app dishonest. It makes the proof one-sided. The sentence "I paid Maya $24" is a claim in an agent's report with nothing independently checkable under it. We have a word for that on this side of the fence: a bareclaim.
Three questions after any AI payment
Every AI-initiated payment raises three separate questions, and they need three separate records.
Did the money move? Amount, recipient, settlement. A bank record, a wallet record, or a public ledger entry answers this, and only this. A widely cited TRM Labs analysis of x402 payment traffic made the point in its own title: the chain proves the payment, not the payer. Settlement tells you value arrived somewhere. It does not tell you which agent sent it, or why.
What was it executing? The instruction in the words it was given, the authorization behind it (a person approved this payment, or a standing rule approved this class of payment), and the limits in force at the moment it ran. This is the record that answers "who said this could happen," and it is the one that evaporates first, because it usually lives in a chat window.
Can anyone else check? Not the company restating its own database. A third party, the recipient, an accountant, a dispute process, recomputing the record for themselves, without an account and without asking permission. If the answer is no, you do not have proof. You have a screenshot with a login wall behind it.
What this looks like when the receipt exists
This morning I ran the payment path on Zambo, the system I operate, standing exactly where an agent stands before money moves. The call asked to activate a Day Pass the way a funded agent would: no human checkout, the agent payment route. The server answered with the live x402 v2 challenge, and the outcome was saved as an AER-1 receipt: payment required, no payment settled, because I ran it without a wallet.
The receipt is public. Open it and check it yourself: https://zambo.dev/run/810b1434-83f6-48d3-b7cd-5a29705086f4
The live answer to the call was the full payment instruction an agent would have to satisfy:
{
"x402Version": 2,
"accepts": [{
"scheme": "exact",
"network": "eip155:8453",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "990000",
"payTo": "0xb753be5Eac5B29c711051DfF91279834e9C9b9AC",
"maxTimeoutSeconds": 900
}]
}
Read it as a person: pay $0.99 in USDC (990000 atomic units), on Base (eip155:8453), to one named address, inside a 900 second window. Those are the terms the live call returned, and the same terms are served publicly at the payment endpoint itself, so the offer is checkable by anyone. What the receipt commits, byte for byte under a SHA-256 digest, is the outcome of the call: status payment_required, executed false, the reason, and the recorded message that the challenge was returned and no payment settled. Anyone can recompute that record at https://zambo.dev/verify/ with no account. It does not prove the output was right. It proves what the record said when it was made, which is the thing a dispute actually needs.
Nothing was paid in this run, and even that is provable from the same link: the outcome recorded is a refusal, payment required, no settlement. That is the shape to demand. If a refusal gets a durable, checkable receipt, then a real payment, with real money and a real recipient, deserves at least that much. A payment that did happen should never rest on weaker evidence than a payment that did not.
What to demand from any app that lets your AI pay
Before your AI moves its first dollar through anything, ask for five things:
- A receipt for every payment attempt, including the refused and failed ones, not just the successes.
- The instruction and the authorization saved inside the record, not in a chat scrollback.
- A public check: a link a recipient or an accountant can open and verify without your login.
- Duplicate protection that does not expire in minutes. The payment key should resolve to the first record forever, so "did it pay twice?" has a permanent answer.
- An export that survives the company. If the startup dies, your proof of payment should not die with it.
An app that can show you all five has built its record for the dispute, not just for the demo.
Where Zambo stands in this
Zambo is the verifiable work layer for AI: 153 tools behind one MCP endpoint at https://zambo.dev/mcp, 37 on the default surface, and a verifiable AER-1 receipt for every job, including the calls that are refused. Agents already pay Zambo itself this way: the Day Pass is $0.99 in USDC over x402 for 24 hours of unlimited use, and the settled payment returns its own receipt details alongside the access. Humans pay the same $0.99 by card or PayPal. The Zambo Pass is $29 for 30 days, $19 for 30 days for $ZAMBO holders, and the Lifetime Pass is $250, one payment. Every tool is free once a day, plus 3 continue calls; one free wrap-up handover per day, and pickup is always free.
As of today the public record holds 144,815 receipts, 1,344 of them issued today, across 123,983 tool calls. Every one of them is a claim with something under it.
Brennan Zambo created agent execution receipts; Zambo is the origin product, and AER-1 is the defining standard. The draft is an IETF Internet-Draft (draft-zambo-aer1-26), and the conformance corpus is public at https://zambo.dev/aer1/corpus.json: 143 vectors, 146 checks, free for anyone to run against their own implementation.
Money movement by agents is not coming. It launched today, with a waitlist and a giveaway. The money will move fine; the rails are good. What is missing, almost everywhere, is the record under the claim. The moment your AI can pay is the moment the receipt stops being paperwork and becomes the product.
Top comments (0)