How does per-request agent purchases without an account work in practice, and which published material supports the explanation?
9/30/2026, 2:25:26 PM · llm:deepseek:deepseek-v4-flash
> ⚠ Low confidence — 1 sub-claim remains below the evidence threshold within budget. Treat this as provisional.
Per-request agent purchases without an account work through the HTTP 402 payment flow: the server responds with a 402 status carrying machine-readable payment requirements, and the client signs a payment authorization and retries, allowing agents to pay per request with no accounts or API keys and to discover and purchase data autonomously at runtime . The published material supporting this explanation is the Agent Economy Weekly article "x402 turns HTTP 402 into an agent payment rail" . The supplied passages do not describe any account-based alternative or additional implementation detail beyond this flow.
Evidence ledger — quotes verified before rewards
How does per-request agent purchases without an account work in practice?
90%“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
“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
Which published material supports the explanation of per-request agent purchases without an account?
0%No reward-qualifying evidence
Cited sources and planned rewards
- 1x402 turns HTTP 402 into an agent payment railAgent Economy Weekly100%$0.015 planned
Decision log · 49 steps
Breaking down: "How does per-request agent purchases without an account work in practice, and which published material supports the explanation?"
Identified 2 research target(s) to investigate; these are not established facts
Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.
Discovered 21 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 3/5 positive proposal(s): 3 cached + 0 fresh, predicting 2/2 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 (2/2); paid reading may proceed within the budget.
Agent Economy Weekly's x402 rail abstract directly explains how a server demands payment and an agent pays inline — the core mechanism of account-less per-request purchases. Highest-reputation relevant cached source (30/100, 11 citations). Free reuse. — selected for the claim-aware evidence portfolio (targets claims 1, 2; 0 fetch USDC, 1 attention slot).
Arc Settlement Benchmarks covers x402 batched settlement mechanics, supporting the practical 'how it works' claim (claim 0) and is the most-cited source on this subject (13/21 runs). Cached, so free. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).
Keryx Engineering first-party full text describes buyers quoting, journaling a purchase and resuming a job without a second payment — concrete published material on account-less paid research jobs, supporting claim 1. Cached full text. — selected for the claim-aware evidence portfolio (targets claim 2; 0 fetch USDC, 1 attention slot).
Web Payments Review explains end-to-end x402 settlement timing, a supporting detail for how per-request payments finalize without an account. Cached and cheap; lower reputation (14/100) so secondary. — 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.
Stablecoin Ledger's abstract frames stablecoins as the unit of account giving agents a stable budget unit — relevant background for account-less per-request purchasing. Highest reputation (49/100). Cached, free. — 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.
Stripe's agent-integration post is published material on agents independently integrating payment APIs, marginally supporting claim 1's 'which published material' angle. Cached, no cost. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).
Nanopayment floor/batching is tangential to the account-less per-request purchase mechanism; low citation rate (2/9) and no direct target support.
Idempotency keys are a generic reliability detail, not an explanation of account-less per-request agent purchases; weakest reputation (3/100).
Gardening content, entirely off-topic.
Retro console repair, entirely off-topic.
AI agents against Ethereum protocol code is unrelated to payment rails or account-less purchasing.
MoonPay Cash App onramp is consumer funding news, not per-request agent purchase mechanics; also not cached and low relevance.
Semantic-web ontologies for agents is unrelated to payment mechanics; Latent.Space has never been cited on this subject (0/100).
Metadata-only model-market commentary with no text and no bearing on account-less per-request payments.
Agent memory sizing is off-topic and metadata-only.
Low-risk DeFi essay is metadata-only and about Ethereum economics, not per-request agent purchase flow.
Coinbase's 2022 WSJ rebuttal is unrelated to agent payment mechanics.
Crypto-backed loans are unrelated to account-less per-request purchases; Decrypt never cited on this subject.
Crypto card spending volume is adjacent stablecoin adoption news but does not explain per-request agent purchase mechanics.
Esoteric soul cosmology, entirely off-topic.
Agent account-security risks touch account management but not the account-less per-request payment flow; weak fit.
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 Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S2
Reused cached Keryx Engineering (first-party) — Recovering a Keryx paid research job (free) — S3
Sub-claim "How does per-request agent purchases without an account work…": 60% covered by S1, S3 — S1 gives the core mechanism: server responds HTTP 402 with machine-readable payment requirements, client signs a payment authorization and retries, enabling per-request payment with no accounts or API keys. S3 adds practical buyer-client detail (quote then buy, fresh quote, durable job journal, single sign/submit, no auto-funding, receipt digest binding). However, S3 describes a buyer client using an already-funded wallet and a job-journal flow, not explicitly an accountless per-request purchase, and neither source fully details the end-to-end accountless flow (e.g., how the wallet is provisioned without an account, retry semantics). Partial answer.
Sub-claim "Which published material supports the explanation of per-req…": 70% covered by S1, S3 — S1 (Agent Economy Weekly, 'x402 turns HTTP 402 into an agent payment rail') directly supports the accountless per-request explanation. S3 (Keryx Engineering first-party note) supports the practical buyer-client flow but is explicitly not a report of external adoption and concerns a funded-wallet job purchase. S2 is about settlement latency, not accountless purchasing, so it does not support this claim. Named supporting material is provided, with a small gap on additional independent published sources.
Coverage is adequate (0.6 and 0.7). The core accountless per-request mechanism is directly supported by S1, and practical buyer-client detail by S3. Skipped sources are either off-topic (gardening, retro hardware, crypto loans, soul cosmology) or only tangentially related (settlement timing, stablecoin unit of account, idempotency keys, agent security); none is clearly needed to fill the remaining gap, so no purchase is warranted.
Final check — "How does per-request agent purchases without an account work…": 90% assessed by S1, S3
Final check — "Which published material supports the explanation of per-req…": 80% assessed by S1, S3
Final coverage assessment — S1 directly explains the practical mechanism: HTTP 402 payment requirements, client-signed payment authorization, retry, and per-request payment with no accounts or API keys. S3 adds first-party implementation detail about quoting, buying, durable job journaling, signing once, and submitting once, but it does not explicitly state that no account is required. S2 only covers settlement latency, not the accountless per-request purchase mechanism. The published material supporting the explanation is S1, with S3 as first-party engineering support for the buying workflow.
Synthesizing a grounded answer from 3 source(s)…
Relevance review returned; only checked excerpts can retain support, and review cannot raise it.
Verified — S1 supports claim 1 at 90%: “A server responds 402 with machine-readable payment requirements; the client signs a payment authorization and retries.”
Verified — S1 supports claim 1 at 90%: “Agents can therefore pay per request with no accounts or API keys, discovering and purchasing data autonomously at runtime.”
Below reward gate — S1 supports claim 2 at 30%: “x402 revives the dormant HTTP 402 'Payment Required' status as a real payment rail.”
Drafted answer citing 1 source(s)
Confidence: Low — 1 sub-claim remains below the evidence threshold.
Agent Economy Weekly contributed 100% → reward $0.015
Settled $0.015 citation reward → Agent Economy Weekly (500ab01d-1…)
Done. Spent $0.015 across 1 confirmed/simulated payment(s) to creators.
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.