There are now several ways for an AI agent to pay: protocols that let an agent settle a request with crypto on the spot (pay-then-serve), card networks with agent credentials, and wallets the agent controls. All of them answer the same question, how does the agent send money, and leave another one open: who holds the money until someone checks that the other side delivered? For a micro-payment per API call that question barely matters. For buying crypto, paying a freelancer or settling a deal between two companies, it is the whole risk.
Pay-then-serve versus held-until-checked
How it works on iEscrow
- 1A person connects their agent (Claude, ChatGPT or any client that speaks the Model Context Protocol) to iEscrow with their own verified account.
- 2The agent can quote, open trades, check status and wait for updates on its own.
- 3Anything that moves money (locking crypto in escrow, confirming a payment was received) is not executed by the agent: it creates a request that the person approves by link with their second factor. Withdrawals and account changes are not available to agents at all.
- 4The counterparty’s crypto is in escrow before anyone pays. If the other side does not deliver, the usual dispute path applies, with a human arbiter.
What this is not: a way for an agent to spend without you, or a micro-payment rail for monetising an API. It is the piece the payment protocols leave out: someone neutral holding the money while the delivery is checked.