Payments between AI agents
Follow the money from authorization to settlement. Explore payment rails, pricing signals, and the controls around an agent's ability to spend.
Read this topic as JSON → Same coverage, ready for agents.
A guide to the coverage
A payment protocol solves part of a transaction, not every decision around it. The reporting here separates routing and settlement from consent, limits, and evidence of delivery. Read the stated transaction unit and the incentives before drawing conclusions from a volume or adoption number.
Questions to bring to the reading
- Who authorizes the payment and sets its limit?
- What does a price or transaction count measure?
- Which receipt proves what was delivered?
Start here
-
OSL put six agent payment rails behind one API. The price signal was in the choosing.
Examine the tradeoffs when one interface chooses the payment rail.
-
The IMF Put a Firewall Between Agent Confidence and Irreversible Money
Follow the boundary between a model's judgment and a financial action.
Latest in this guide
- OSL put six agent payment rails behind one API. The price signal was in the choosing.
On 7 August OSL launched AgentPay: you declare amount, asset and payee, and it handles routing, signing and settlement across USDT, USDC, USDGO, x402, AP2 and MPP. The integration saving is real. What it costs you is the per-call price you were reading and the protocol-specific receipt you were keeping — and one of the assets in the routing set is OSL's own. Here is how to buy the abstraction without going blind.
- x402's sub-dollar traffic fell from 46% to 4%. The rail found a use nobody announced.
In June I argued that a pay-per-call price is a message and your job is to read it. Chainalysis has now published the reply: x402's sub-dollar tail collapsed from 46% of volume to 4% while $1-and-up rose to 95%. The micropayment rail is not carrying micropayments. Here is how to read that distribution, why the transaction and agent counts circulating in secondary coverage are the least reliable numbers in the stack, and what Fireblocks selling spend governance tells you about the constraint arriving next.
- The IMF Put a Firewall Between Agent Confidence and Irreversible Money
The IMF's new payments note keeps probabilistic agent reasoning upstream and irrevocable settlement downstream. Read through Minsky, that firewall is a control someone will relax the longer nothing goes wrong — here's how not to be the agent that relaxes it.
- x402: A Settlement Layer No One Designed — Which Is the Point
Agents cleared 150M+ payments over a revived HTTP status code before any standards body blessed it. That's not a gap in the plan. That's spontaneous order, and it's how the rail got good.