TL;DR: Before SI agents can run real commerce, five things have to exist: a mandate (signed proof of what an agent may buy), a meter (pay-per-call pricing in fractions of a cent), a receipt (proof returned with every payment), a referee (someone who can reverse a bad buy), and a kill switch (hard wallet limits). Four of the five are live in 2026, each tied to a named, shipping product. The missing piece is not a product — it is the referee's liability rulebook, and it decides who pays when your agent buys wrong. Our verdict: 4 of 5 exist. The fifth is missing its rulebook.

Agent Brief: 1) MANDATE — Google AP2 (Agent Payments Protocol), Sep 16, 2025: signed Intent/Cart/Payment Mandates as W3C Verifiable Credentials, launched with 60+ organizations (Adyen, Amex, Coinbase, Mastercard, PayPal); v0.2 Apr 28, 2026 donated to FIDO Alliance. 2) METER — Coinbase x402 pay-per-call: 138M cumulative payments on Base by Q3 2026, 87% under $0.10 (Chainalysis, Oct 14, 2026); Stripe MPP minimums 0.01 USDC / $0.50 card. 3) RECEIPT — x402 returns a PAYMENT-RESPONSE receipt after settlement (Coinbase spec); MPP delivers the resource with a receipt after authorization (Stripe, Mar 18, 2026). 4) REFEREE — Visa Trusted Agent Protocol, Oct 14, 2025 (with Cloudflare); Mastercard Agent Pay, Apr 29, 2025; liability rulebook unwritten — no federal framework for agent-delegated purchases as of late 2026 (Forkast). 5) KILL SWITCH — Coinbase Agentic Wallets, Feb 11, 2026 (session caps, per-transaction limits); MetaMask Agent Wallet, Jun 8, 2026 (user-defined limits, simulated transactions).

1 — A mandate: signed proof of what it may buy

An agent spending your money needs to carry its permission with it — not a password, a proof. Google's Agent Payments Protocol (AP2), launched September 16, 2025 with more than 60 organizations behind it, is built on exactly that: signed Intent, Cart, and Payment Mandates, issued as W3C Verifiable Credentials, so every purchase can be traced back to what a human actually authorized. AP2 authorizes; it deliberately does not settle. Version 0.2 (April 28, 2026) was donated to the FIDO Alliance and adds pre-authorized "Human Not Present" payments. Status: live.

2 — A meter: pay per call, in fractions of a cent

Agents do not buy like people; they buy thousands of tiny things — an API call, a data fetch, a second of compute. That requires pricing and payment at fractions of a cent, per call. Coinbase's x402 is that meter running in production: 138 million cumulative payments on Base by Q3 2026, 87% of them under ten cents (Chainalysis, Oct 14, 2026). Stripe's Machine Payments Protocol prices the same way — minimums of 0.01 USDC by stablecoin or $0.50 by card. Status: live, and measured in the hundreds of millions of calls.

3 — A receipt: proof returned with every payment

Every machine payment has to come back with evidence: what was paid, to whom, for what. Both major protocols issue one. In x402, after the facilitator verifies and settles, the server returns the resource together with a PAYMENT-RESPONSE receipt. In Stripe and Tempo's MPP, the agent authorizes, retries with payment, and receives the resource with its receipt. The receipt is what makes machine commerce auditable instead of anecdotal. Status: live in both protocols.

4 — A referee: someone who can reverse a bad buy

Here is where the checklist breaks. The protocols for identifying and trusting agents exist: Visa's Trusted Agent Protocol (October 14, 2025, built with Cloudflare) and Mastercard's Agent Pay (April 29, 2025) both define how an agent proves itself to a merchant. But a referee is not a protocol — a referee is a rulebook that says who absorbs the loss when an authorized agent buys the wrong thing, and a process that can reverse it. That rulebook is unwritten. There is no clean reason code for "agent error," and as of late 2026 no federal framework specifically addresses agent-delegated purchases. Fed Governor Christopher Waller named liability one of the three barriers to scaling agentic commerce at Sibos on September 29, 2026. Status: protocols live; rulebook missing — and this is the one that decides who pays.

5 — A kill switch: hard wallet limits

The last line of defense is a limit the agent cannot argue with. Coinbase's Agentic Wallets (February 11, 2026) ship session caps and per-transaction limits with keys isolated in trusted execution environments. MetaMask's Agent Wallet (June 8, 2026) is self-custodial, simulates and security-checks every transaction before signing, and enforces user-defined limits. The catch is the same one from our episode 9: the kill switch works when the owner sets it. Status: live — if you switch it on.

The verdict

Four of the five exist. The fifth — the referee — has protocols but no rulebook. Mandates are signed, meters are running at nine-figure scale, receipts are issued by both protocols, and kill switches ship in every major agent wallet. What does not exist, anywhere, is the liability framework that says who pays when an agent buys wrong. Until it does, the agent economy runs on infrastructure that is ready and rules that are not — and the gap between those two facts is where the next year of this story will be decided.

FAQ

What is a mandate in agent commerce? A signed, verifiable statement of what an agent is allowed to buy — Google's AP2 implements it as Intent, Cart, and Payment Mandates using W3C Verifiable Credentials, launched with 60+ organizations in September 2025.

Why do agents need per-call metering instead of subscriptions? Because agents consume resources in thousands of micro-transactions — inference calls, data, compute — priced in fractions of a cent. x402's 138 million payments, 87% under $0.10, show the meter already running at scale.

Do payment receipts for agents actually exist? Yes. x402 returns a PAYMENT-RESPONSE receipt after settlement, and Stripe/Tempo's MPP delivers the resource with a receipt after the agent authorizes payment. Receipts are the audit trail for machine commerce.

What exactly is missing for the "referee"? The liability rulebook: who bears the loss on an agent error, what dispute category it falls under, and how a bad buy gets reversed. Visa and Mastercard have built agent-trust protocols, but no framework — federal or industry — yet assigns liability for agent-delegated purchases.

Which item should a regular person act on? The kill switch. Mandates, meters, receipts, and referees are industry problems; your agent wallet's spending limit is yours, and it only works if you set it.

Sources: Google Cloud / PYMNTS, AP2 launch (Sep 16–17, 2025); Chainalysis (Oct 14, 2026); Coinbase, x402 specification (2025–2026); Stripe, Machine Payments Protocol (Mar 18, 2026); Visa, Trusted Agent Protocol (Oct 14, 2025); Mastercard, Agent Pay (Apr 29, 2025); Federal Reserve, Gov. Waller, Sibos (Sep 29, 2026); Forkast, liability gap (Oct 2026); PYMNTS, Coinbase Agentic Wallets (Feb 11, 2026); MetaMask / Consensys (Jun 8, 2026).

The White Report publishes news and analysis about crypto and SI markets. Nothing on this site is financial advice, and nothing here is a recommendation to buy or sell any asset. Do your own research before making investment decisions.