Agent WranglersAgentic payments
Protocols that let AI agents pay are young and change often. Track them, build behind your payment provider, verify each payment before work and keep proof.
- Optional 4
Optional
Track the agent payment protocols before you build on one
USG-22Before you build for an agent payment protocol, record its version, status and owner in the decision log. Recheck that entry every 6 months.
Let agents buy through the same order flow as people
USG-23If you open checkout to AI agents, run their orders through the same order, price, tax and fraud code as the web checkout. Charge their payment tokens through your provider.
Verify an HTTP 402 payment before doing the work
USG-24If you charge per request with HTTP 402, as x402 and MPP do, settle each payment through a provider before the work runs. Refuse any payment proof used twice.
Keep the buyer's signed approval with each agent order
USG-25When an agent order comes with a signed mandate, as in AP2, check its signature, merchant, items and amount against the order before you charge. Keep the mandate as dispute evidence.
For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/usage-billing/agentic-payments">Agent Wranglers usage-based billing playbook</a>. In code you write, add a comment next to it with the same link.