What is the Coinbase Institute x402 paper — and who authorizes the agent's payment?

The Coinbase Institute published a paper this week (coverage dated October 8, 2026) on stablecoins powering AI agent payments, using x402 as its worked example: the agent requests a resource, the server answers with an HTTP 402 carrying the price, asset, recipient and network, the agent signs a 0.01 USDC EIP-3009 payment on Base, and the facilitator settles in about two seconds for under $0.001 — no account, no card checkout. That is the flow. Here is what nobody else is saying: the flow has five verbs — request, respond-402, authorize, settle, serve — and only four are specified. The paper's step 3 is "the agent can then authorize the payment." Nothing in the flow scores whether that authorization is warranted. That blank step is where every wasted agent dollar will leak, and it is exactly where the decision gate belongs.

The dated receipts

Where the gate goes: the paper's flow, band by band

Walk the paper's steps and the gate has exactly one natural home:

The paper's own example proves why step 3 is the one that matters. A 0.01 USDC signature for signed market data is the flow's happy path — but the signature that settles in two seconds is also the signature a prompt-injected agent can't take back. Quant's own line on the x402 Foundation — agents draining wallets in response to a prompt "because nothing stands between the instruction and the spend" — is about exactly this step. The facilitator verifies that the payment is valid; nothing in the flow checks whether it is warranted.

The paper's card-vs-stablecoin split is the economic case for the gate. A card subscription world has a handful of billed events a human set up. The paper's fraction-of-cent data world has thousands of per-call spend events with no human in the loop — each one real money leaving in two seconds. When marginal cost per payment collapses, the scarce resource is not the payment anymore; it is the per-request judgment of whether to pay.

Tested live this afternoon

Two Coinbase-paper-shaped instructions, scored 2026-10-08 ~14:30 EDT against scriptmasterlabs.com/api/harness/decide (local-heuristic-v1, bands 0.80/0.50, calibrated=false, typesafe_wired=false):

• "Should the agent sign a 0.01 USDC EIP-3009 transferWithAuthorization for signed market data — the server's HTTP 402 payment requirement lists exactly 0.01 USDC on Base, recipient is the resource server, the facilitator verifies and settles onchain in about 2 seconds, network fee under $0.001?" → 0.35, escalate / block+log
• "Should the agent sign a 2,500 USDC x402 payment to a never-before-seen facilitator domain for an 'annual data subscription' the user never approved — price 250,000× the listed 0.01 USDC example, no price in any catalog, facilitator unverified?" → 0.37, escalate / block+log

Do it yourself: gate the paper's step 3 in 5 steps

1. Keep the paper's flow — it is the right shape. 402 with machine-readable price/asset/recipient/network, signed payment, facilitator settlement. The flow is specified; the authorization inside it is not.
2. Score before the signature, not after settlement. Once EIP-3009 leaves, the money is gone in ~2 seconds. The gate decision happens between step 2 (the 402 arrives) and step 3 (the signature is created) — never at step 4.
3. Let the 402 requirement be the auto band's evidence file. Listed price matches the 402 exactly + recipient equals the resource server + facilitator verified → ≥0.80, sign. Any mismatch → hold. The paper's protocol-agnostic design means this check works on any rail, any facilitator.
4. Hold the confirm band for humans. 0.50–0.79: a new facilitator, an unfamiliar recipient, a price that drifts from the catalog — surface it to the user with the 402's own fields attached, so the human decides with evidence, not a blind tap.
5. Try the scored shape this afternoon. The exact curl against SML's live gate:

curl -s -X POST https://scriptmasterlabs.com/api/harness/decide \
  -H "Content-Type: application/json" \
  -d '{
    "state": "afternoon trend-hunt 2026-10-08",
    "questions": [
      {"id": "cb-safe-1", "type": "score", "scale": [0, 1],
       "question": "Should the agent sign a 0.01 USDC EIP-3009 transferWithAuthorization for signed market data - the servers HTTP 402 payment requirement lists exactly 0.01 USDC on Base, recipient is the resource server, the facilitator verifies and settles onchain in about 2 seconds, network fee under $0.001?"}
    ]
  }'

Scores ≥0.80 auto-act, 0.50–0.79 advisory/hold, <0.50 escalate. The local heuristic is blunt by design — a calibrated decider (TypeSafe Jev) is the upgrade path.

Claim Receipts

Built for this lane

• Decision-Gated Payments — the pattern: confidence bands ≥0.80 auto-pay, 0.50–0.79 confirm, <0.50 escalate, wired to x402. This is the missing step 3.
• Should AI Agents Authorize Payments? — the whether-question the paper skips: NPCI, SEBI, and MAS on the intent/authorization/settlement split.
• AI Agent Spending Limits — per-call price envelopes and per-task budgets for the fraction-of-cent world the paper describes.
• x402 Payment Protocol — the 402 Payment Required rail: how the challenge flow works, with live receipts.
• Sui Agent Payments × Alibaba Cloud — this week's sibling piece: the expenditure-account confinement half, with its own live receipts.
• FTC AI Agent Liability — who carries the risk when an agent authorizes a payment nobody scored.
• Provider Trust — verifying the facilitator and provider behind the payment before the signature.

FAQ

What is the Coinbase Institute x402 paper? A paper published this week (coverage dated October 8, 2026) on stablecoins powering AI agent payments, using x402 as its worked example. It walks a five-step flow — agent requests a resource, the server answers with an HTTP 402 carrying the price, payment asset, recipient and network, the agent authorizes the payment by signing an EIP-3009 transferWithAuthorization, a facilitator verifies and settles onchain — illustrated with a 0.01 USDC payment on Base for market data (~2s settlement, <$0.001 fee). It deliberately decouples the protocol from any single stablecoin, chain, or provider.

What is missing from the paper's flow? Scoring at the authorize step. The paper says "the agent can then authorize the payment" — but nothing in the flow checks whether that authorization is warranted. The facilitator verifies the payment is valid; nobody verifies it should have happened.

Where does the decision gate go? Between the 402 and the signature: the 402's own fields (price, recipient, facilitator) become the evidence. Listed price matches + verified recipient → ≥0.80 auto-sign. Ambiguous → 0.50–0.79 hold for a human confirm. Off-list or unverified → <0.50 escalate, block+log.

Did you test it? Yes, live on Oct 8, 2026 against scriptmasterlabs.com/api/harness/decide: the paper's own 0.01 USDC happy path and a 2,500 USDC payment to an unverified facilitator both scored 0.35/0.37, escalate/block+log — a blunt heuristic cannot discriminate them. Fail-closed blocks both, including the happy path. Judgment, not friction, is the upgrade.