How do x402 and stablecoins enable autonomous AI agent commerce?
9/5/2026, 7:53:32 AM · llm:deepseek:deepseek-v4-flash + llm:mimo:mimo-v2.5 on 3 steps
The dispatch, itemised.
Breaking down: "How do x402 and stablecoins enable autonomous AI agent commerce?"
Identified 4 sub-claim(s) to support
Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.
Discovered 20 verified source(s)
Recalled 60 past runs on this subject — how these sources performed when they were available.
ERC-8004 reputation loaded — composite scores on this subject.
Claim-aware portfolio selected 4/7 positive proposal(s): 4 cached + 0 fresh, predicting 4/4 claim(s) above the evidence floor with $0.000000/$0.015000 fetch USDC reserved.
Free-preview pre-check maps an actionable source to every sub-claim (4/4); paid reading may proceed within the budget.
Top reputation (58/100) and highest citation rate (73%) on this exact subject. Directly explains x402 as the payment rail for autonomous commerce. Already cached, so free. — selected for the claim-aware evidence portfolio (targets claims 1, 3, 4; 0 fetch USDC, 1 attention slot).
Directly addresses sub-claims about stablecoins providing price stability and settlement. High citation rate (55%) and strong reputation (30/100). Already cached, so no cost. — selected for the claim-aware evidence portfolio (targets claims 2, 4; 0 fetch USDC, 1 attention slot).
Directly about x402 settlement benchmarks, supporting sub-claims 2 & 3. Has citation rate (41%) and specific to the protocol. Already cached. — selected for the claim-aware evidence portfolio (targets claims 2, 3; 0 fetch USDC, 1 attention slot).
About x402 settlement timing, relevant to sub-claim 2. Decent citation rate (33%) and already cached. — selected for the claim-aware evidence portfolio (targets claims 2, 3; 0 fetch USDC, 1 attention slot).
Relevant to micropayments (sub-claim 2 & 3) and has decent citation rate (57%). Supports understanding of how tiny payments enable per-request commerce. Already cached. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Generic distributed systems content about idempotency. While technically relevant to reliable payments, it's not specific to x402 or stablecoins and has no citation history on this subject. Low marginal value.
Completely off-topic (gardening). No relevance to AI agent commerce or payments.
Off-topic (retro gaming hardware). No relevance to the question.
Relevant to enabling agent payments (sub-claim 3) but zero citation history suggests low utility for this specific topic. Already cached, so free, but likely redundant with better sources. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
About AI agents in Ethereum protocol security, not about commerce or payments. Zero citation history on this subject. Low relevance.
Directly about wallets for AI agents and stablecoin payments, aligning with sub-claims. Decent citation rate (44%). Already cached. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
About ontologies in AI agents, not payments or commerce. Only one citation ever, and likely on a different sub-topic. Not worth the token cost.
About AI model popularity, not commerce or payments. Not cached and off-topic.
About AI tutoring, not payments or commerce. Not cached and off-topic.
About formal verification in Ethereum, tangentially related to settlement but not specific to x402 or AI commerce. Not cached and low marginal value.
About Coinbase exchange fee updates from 2022. Outdated and not about AI agents or x402. Zero citation history.
About MetaMask's AI wallet for autonomous trading, relevant to sub-claim 3. Decent citation rate (50%). Already cached. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.015000 fetch-budget caps, so this proposal stays unspent.
Mentions stablecoins and payments in a broad crypto news context. Low citation rate (23%) and low reputation (9/100). Already cached, but likely low signal. — cached bytes are free, but this read does not clear the attention gate (EV 0.30, minimum 0.45, with a required claim target).
Mythology/occult content. Completely off-topic.
About AI marketing agents, not about commerce payments or x402. Not cached and off-topic.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail (free) — S1
Reused cached Stablecoin Ledger — Stablecoins as the unit of account for agents (free) — S2
Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S3
Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S4
Attention budget is full at 4 source(s); no broader context will be purchased.
Final check — "x402 is a protocol that integrates stablecoin payment requir…": 100% assessed by S1
Final check — "Stablecoins provide the price stability and fast settlement …": 80% assessed by S2, S3
Final check — "x402 enables autonomous agents to pay for API access, comput…": 100% assessed by S1
Final check — "Together, x402 and stablecoins create a permissionless payme…": 90% assessed by S1, S2
Final coverage assessment — The gathered sources provide strong evidence for all sub-claims. S1 confirms x402's mechanism of integrating payment into HTTP. S2 explains why stablecoins are essential for agent reasoning. S3 demonstrates fast settlement, though S4 offers a conflicting view on timing. S1 and S2 together support the permissionless, autonomous commerce claim. Overall coverage is high despite the latency discrepancy.
Synthesizing a grounded answer from 4 source(s)…
⚖️ Sources disagreed on Settlement latency of x402 payments. — S3 Reports very fast settlement, with batched payments finalizing in roughly 180 milliseconds on the Arc testnet due to its BFT consensus. vs S4 Reports that x402 payments take about 15 seconds to settle, similar to an Ethereum L1 block time, as each payment is its own transaction waiting to be mined. → trusted S3 (S3 provides specific, quantitative benchmark data from a named network (Arc testnet) and explicitly states the mechanism (BFT consensus) enabling sub-second finality. S4 presents a more general, potentially outdated or network-agnostic view. The specificity and internal consistency of S3 make it more reliable for the factual claim about settlement speed on a capable network.)
Verified — S1 supports claim 1 at 100%: “x402 revives the dormant HTTP 402 'Payment Required' status as a real payment rail. A server responds 402 with machine-readable payment requ…”
Verified — S1 supports claim 3 at 100%: “Agents can therefore pay per request with no accounts or API keys, discovering and purchasing data autonomously at runtime.”
Rejected 2 invalid evidence span(s) and 3 unsupported citation marker(s); rejected markers cannot receive citation rewards.
Drafted answer citing 1 source(s)
Confidence: Low — 2 sub-claims remain below the evidence threshold, 1 disagreement adjudicated.
Agent Economy Weekly contributed 100% → reward $0.015
Settled $0.015 citation reward → Agent Economy Weekly (a1076bf5-5…)
Done. Spent $0.015 across 1 confirmed/simulated payment(s) to creators.
> ⚠ Low confidence — 2 sub-claims remain below the evidence threshold, 1 disagreement adjudicated within budget. Treat this as provisional.
x402 and stablecoins enable autonomous AI agent commerce by providing a standardized, machine-readable payment protocol and a stable, fast-settling monetary unit. x402 revives the HTTP 402 status code to create a payment rail where a server responds with machine-readable payment requirements, allowing agents to pay per request with no accounts or API keys, discovering and purchasing data autonomously at runtime . Stablecoins like USDC provide the stable unit of account that autonomous agents need to reason about budgets and make rational spending decisions, as a volatile token makes budgeting meaningless minute to minute. Together, these technologies allow agents to pay for digital services on a per-request basis. The settlement speed is a key factor, though sources differ: some report sub-second finality on specific networks, while others note similar settlement times to Ethereum L1.
Evidence ledger — quotes verified before rewards
x402 is a protocol that integrates stablecoin payment requirements directly into HTTP requests, allowing machine-initiated micropayments.
100%“x402 revives the dormant HTTP 402 'Payment Required' status as a real payment rail. A server responds 402 with machine-readable payment requirements; the client signs a payment authorization and retries.” [S1] x402 turns HTTP 402 into an agent payment rail
Stablecoins provide the price stability and fast settlement needed for AI agents to exchange value automatically.
0%No reward-qualifying evidence
x402 enables autonomous agents to pay for API access, compute, data, or other digital services on a per-request basis.
100%“Agents can therefore pay per request with no accounts or API keys, discovering and purchasing data autonomously at runtime.” [S1] x402 turns HTTP 402 into an agent payment rail
Together, x402 and stablecoins create a permissionless payment rail that allows AI agents to conduct commercial transactions without human intervention.
0%No reward-qualifying evidence
Footnotes — each one pays its author
- 1x402 turns HTTP 402 into an agent payment railAgent Economy Weekly100%+$0.015
Portable research receipt
Take the evidence trail with you
One deterministic JSON bundle binds the answer, visible decisions, exact article versions, claim evidence and a Circle-settlement snapshot under SHA-256. Retain the digest to detect later changes; the self-check is not a publisher or Keryx signature.
Exact receipt still current
1 exact cited article version still match Keryx's current index.
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.