How does HTTP 402 work as a payment rail for autonomous agents?
7/29/2026, 10:57:32 AM · llm:deepseek:deepseek-v4-flash
The dispatch, itemised.
Breaking down: "How does HTTP 402 work as a payment rail for autonomous agents?"
Identified 4 sub-claim(s) to support
Discovered 20 verified source(s)
Recalled 40 past runs on this subject — how these sources performed when they were available.
ERC-8004 reputation loaded — composite scores on this subject.
Overview of x402 payment finalization; cited in 34% of past runs.
Stablecoins as unit of account for agents; cited in 69% of past runs with high weight.
Directly measures x402 settlement latency on Arc; cited in 59% of past runs.
Directly discusses x402 and HTTP 402 as agent payment rail; cited in 63% of past runs with high weight.
Idempotency keys prevent double-spends, important for payment rails; cited in 54% of past runs but lower weight.
Covers nanopayments and batching relevant to micropayments for 402; cited in 51% of past runs.
Not directly relevant to HTTP 402; no historical citations on this subject.
Tangential: covers AI agents on Ethereum but not specifically HTTP 402 payment rail.
Tangential: crypto news but not specifically about HTTP 402; moderate historical citation.
Not directly relevant to HTTP 402; regulatory news.
Low relevance and low historical citation rate on this subject.
Low relevance and low historical citation rate on this subject.
Not directly relevant to HTTP 402; low historical citation on this subject.
Not directly relevant to HTTP 402; focuses on ML and robotics.
Focuses on AI models, not HTTP 402 or agent payment rails.
Not directly relevant to HTTP 402; covers cryptography and formal verification.
Irrelevant: focuses on gardening, not HTTP 402 or autonomous agents.
Irrelevant: focuses on retro gaming hardware, not HTTP 402.
Irrelevant: esoteric content, not related to HTTP 402.
Irrelevant: covers space, travel, and lifestyle, not HTTP 402.
Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)
Reused cached Web Payments Review (free) — S1
Reused cached Stablecoin Ledger (free) — S2
Reused cached Arc Settlement Benchmarks (free) — S3
Reused cached Agent Economy Weekly (free) — S4
Reused cached Distributed Systems Notes (free) — S5
Reused cached Onchain Micropayments Digest (free) — S6
Sub-claim "HTTP 402 is an HTTP status code indicating payment is requir…": 90% covered by S4 — S4 explicitly states that HTTP 402 'Payment Required' status is revived as a payment rail, implying it indicates payment is required.
Sub-claim "In the context of autonomous agents, the 402 response includ…": 90% covered by S4 — S4 describes the server responding with machine-readable payment requirements and the client signing a payment authorization and retrying, which the agent does automatically.
Sub-claim "Autonomous agents can use a built-in wallet to send payment,…": 40% covered — No gathered source explicitly mentions a built-in wallet or cryptocurrency address in the context of HTTP 402; it is only implied by references to transactions and stablecoins.
Sub-claim "Upon successful payment confirmation, the server grants acce…": 60% covered by S4 — S4 implies that after payment authorization and retry, access is granted, but does not explicitly state server action upon confirmation.
Sub-claim 3 has coverage below 0.5 and lacks explicit details on agent wallet and cryptocurrency payment. Latent.Space (price 0.004) likely addresses agent economics and payment infrastructure, fitting the remaining budget. Other skipped sources are either irrelevant or less directly applicable.
Filling gap — buying Latent.Space ($0.004)…
Paid $0.004 to Latent.Space (settled c24c6c6b-0…) — S7
Final check — "HTTP 402 is an HTTP status code indicating payment is requir…": 100% assessed by S4
Final check — "In the context of autonomous agents, the 402 response includ…": 100% assessed by S4
Final check — "Autonomous agents can use a built-in wallet to send payment,…": 60% assessed by S2, S4
Final check — "Upon successful payment confirmation, the server grants acce…": 90% assessed by S4
Final coverage assessment — All sub-claims have coverage above 0.4 based on gathered sources, particularly S4 which explicitly describes HTTP 402 revival as a payment rail for autonomous agents. S2 and S6 provide supporting context on stablecoins and micropayments.
Synthesizing a grounded answer from 7 source(s)…
⚖️ Sources disagreed on Settlement time for x402 payments — S1 x402 payments take about 15 seconds to settle, similar to Ethereum L1 block time vs S3 x402 batched settlements finalize in roughly 180 milliseconds (median 178ms, p95 240ms) on Arc testnet → trusted S3 (S3 provides specific, measured latency data from a testnet, while S1 makes a general statement. The conflict likely arises from different underlying networks (Ethereum L1 vs. Arc BFT). S3 is more precise for the context of batched settlements on a modern fast-finality chain.)
Verified — S4 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 — S4 supports claim 2 at 100%: “the client signs a payment authorization and retries. Agents can therefore pay per request with no accounts or API keys, discovering and pur…”
Verified — S2 supports claim 4 at 100%: “instant final settlement means an agent can pay and immediately receive a resource without counterparty risk.”
Rejected 1 invalid evidence span(s) and 2 unsupported citation marker(s); rejected markers cannot receive citation rewards.
Drafted answer citing 2 source(s)
Confidence: Low — 1 sub-claim remain below the evidence threshold, 1 disagreement adjudicated.
Stablecoin Ledger contributed 30% → reward $0.006
Agent Economy Weekly contributed 70% → reward $0.014
Settled $0.006 citation reward → Stablecoin Ledger (4a009644-3…)
Settled $0.014 citation reward → Agent Economy Weekly (874a384e-e…)
Done. Spent $0.024 across 3 payment(s) to creators.
Stablecoin Ledger
batched
Agent Economy Weekly
batched
> ⚠ Low confidence — 1 sub-claim remain below the evidence threshold, 1 disagreement adjudicated within budget. Treat this as provisional.
HTTP 402 is an HTTP status code indicating payment is required to access a resource . In the context of autonomous agents, the server responds with a 402 status and machine-readable payment requirements; the agent can then automatically sign a payment authorization and retry the request, enabling per-request payments without accounts or API keys . Agents can use a built-in wallet to send payment, such as cryptocurrency (e.g., USDC) to the address provided in the payment request . Upon successful payment confirmation, the server grants access to the requested resource, allowing the agent to immediately receive the data . Settlement times vary: on Ethereum L1, a payment may take ~15 seconds, while on networks like Arc, batched settlements finalize in under 200 milliseconds.
Evidence ledger — quotes verified before rewards
HTTP 402 is an HTTP status code indicating payment is required to access a resource.
100%“x402 revives the dormant HTTP 402 'Payment Required' status as a real payment rail. A server responds 402 with machine-readable payment requirements” [S4] Agent Economy Weekly
In the context of autonomous agents, the 402 response includes a payment request that the agent can process automatically.
100%“the client signs a payment authorization and retries. Agents can therefore pay per request with no accounts or API keys, discovering and purchasing data autonomously at runtime.” [S4] Agent Economy Weekly
Autonomous agents can use a built-in wallet to send payment, such as cryptocurrency, to the provided address.
0%No reward-qualifying evidence
Upon successful payment confirmation, the server grants access to the requested resource.
90%“instant final settlement means an agent can pay and immediately receive a resource without counterparty risk.” [S2] Stablecoin Ledger
Footnotes — each one pays its author
- 2Stablecoin Ledger30%+$0.006
- 4Agent Economy Weekly70%+$0.014
Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.