Archived dispatch

How long do x402 payments take to finalize?

Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.

· llm:mimo:mimo-v2.5

§ IIThe reading2 cited
Lowconfidence— Contains synthetic demo material; its measurements cannot support factual conclusions.deep researchpreview plan 1/1 claimsportfolio 2/3 · evidence 100%

Illustrative demo content: synthetic sources and measurements are not factual research evidence. Source provenance and payment status are separate; inspect the receipt for settled, pending or simulated payments. Settlement does not authenticate a source's claims.

> ⚠ Low confidence — 1 source disagreement remains unresolved; coverage scores do not resolve conflicting evidence within budget. Treat this as provisional.

The time for x402 payments to finalize depends on the underlying network. On Ethereum L1, an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time . On Arc, x402 batched settlements finalize in roughly 180 milliseconds, with a median of 178ms and a 95th percentile of 240ms .

Evidence ledger — recorded source excerpts

Research targets are unverified topics. Coverage is an estimate of excerpt support, not proof of entailment, factual truth or a complete answer.

  1. Requested topic (unverified): “How long do x402 payments take to finalize?”

    0% estimated

    No qualifying excerpt recorded

No inspectable non-demo excerpts are recorded for source inspection.

Research evidence matrix

Compare unverified research targets with cited sources and inspect recorded excerpts. An empty cell means no inspectable excerpt was recorded; it does not establish whether a claim is true, false, or disputed. Coverage and agent confidence do not prove entailment, measured accuracy or complete synthesis.

Research target by cited source evidence matrix
Research target (unverified)Inspection status[S1] How long do x402 payments take to finalize?Publication: Web Payments ReviewPublished: Not recorded[S2] Measuring x402 settlement latency on ArcPublication: Arc Settlement BenchmarksPublished: Not recorded
How long do x402 payments take to finalize?Illustrative demo excerpt
Inspect 1 excerpt
In our reading, an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own transaction waiting to be mined into a block.
Inspect 1 excerpt
Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms).

Reference export

2 article references. Recorded titles, links and dates; observed scholarly records also include supplied authors, DOI and journal metadata with read limits. Review metadata before using in a paper. Import RIS into Zotero with File → Import.

Cited sources and references

Spent$0.02
To creators100%
Decisions0 bought · 2 cached · 19 skipped
llm:mimo:mimo-v2.5Arc Testnet · historical
Decision log · 48 steps
§ IThe decision$0.02 settled / $0.04
50%$0.02 under cap
Decompose

Breaking down: "How long do x402 payments take to finalize?"

Decompose

Identified 1 research target(s) to investigate; these are not established facts

Decompose

Deep mode: up to 4 paid/cached reads plus one bounded gap-expansion pass when needed.

Discover

Discovered 21 verified source(s)

Discover

Recalled 60 past runs on this subject — how these sources performed when they were available.

Discover

ERC-8004 reputation loaded — composite scores on this subject.

Pre-check

Claim-aware portfolio selected 2/3 positive proposal(s): 2 cached + 0 fresh, predicting 1/1 claim(s) above the evidence floor with $0.000000/$0.020000 fetch USDC reserved.

Pre-check

Free-preview pre-check maps an actionable source to every sub-claim (1/1); paid reading may proceed within the budget.

DecideCACHE
Web Payments Review — How long do x402 payments take to finalize?$0.002 · EV 90%

Abstract title exactly matches the query 'How long do x402 payments take to finalize?' and promises an overview of end-to-end settlement timing. Cached and directly addresses target 0. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).

DecideCACHE
Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc$0.003 · EV 80%

Abstract directly measures x402 settlement latency on Arc, perfectly matching the query about finality timing. Cached and free to reuse for target 0. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).

DecideSKIP
Stablecoin Ledger — Why USDC settles instantly onchain$0.003 · EV 10%

Abstract discusses USDC instant settlement on L2s but does not address x402 payment finality specifically. No direct help for the query.

DecideSKIP
Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail$0.004 · EV 60%

Abstract explains x402 as an agent payment rail, directly relevant to understanding the x402 protocol. Cached, so free to reuse for target 0. — the claim-aware portfolio chose a stronger, less redundant set inside the 4-source attention and $0.020000 fetch-budget caps, so this proposal stays unspent.

DecideSKIP
Onchain Micropayments Digest — Nanopayments and the $0.000001 floor$0.005 · EV 20%

Focuses on nanopayment floors and batching, not on finality timing for x402. Off-topic for the specific question.

DecideSKIP
Distributed Systems Notes — Idempotency keys prevent double-spends$0.003 · EV 10%

Discusses idempotency keys for double-spend prevention, not settlement latency. Not relevant to finality timing.

DecideSKIP
Garden & Soil Monthly — Building a no-dig raised bed$0.002 · EV 0%

Gardening content, completely unrelated to x402 payments or settlement.

DecideSKIP
Retro Game Hardware — Recapping a 1990s console$0.002 · EV 0%

Retro gaming hardware repair, no relevance to x402 or payment finality.

DecideSKIP
Stripe Blog — Stripe Projects adds new agent integrations, more providers, and custom developer controls$0.002 · EV 30%

Abstract mentions Stripe Projects and agent integrations but does not discuss x402 settlement timing. No direct evidence for the query.

DecideSKIP
Ethereum Foundation Blog — The triage is the product: running AI agents against Ethereum's protocol code$0.002 · EV 10%

Focuses on AI agents for Ethereum protocol security, not payment settlement speed. Unrelated to x402 finality.

DecideSKIP
Cointelegraph.com News — Crypto payments barely register among euro area merchants, ECB finds$0.002 · EV 20%

News about crypto payment adoption rates, not about x402 settlement latency. Not helpful for the specific timing question.

DecideSKIP
Latent.Space — Ontologies Are So Back: Why AI Agents Are Reviving the Semantic Web$0.004 · EV 10%

Discusses AI agents and semantic web, not payment finality or x402. No relevance to the query.

DecideSKIP
Simon Willison's Weblog — Anthropic’s best AI model struggles to attract users as cheaper tools thrive$0.003 · EV 0%

Metadata only, about AI model usage trends, not x402 or payments. No value for the query.

DecideSKIP
Hugging Face - Blog — TutorMoments: Do AI tutors know when to help and when to hold back?$0.003 · EV 0%

Metadata only, about AI tutors, not relevant to x402 or payment finality.

DecideSKIP
Vitalik Buterin's website — Low-risk defi can be for Ethereum what search was for Google$0.004 · EV 10%

Metadata only, about low-risk DeFi, not x402 settlement timing. No direct help.

DecideSKIP
The Coinbase Blog - Medium — How Coinbase Protects Users From Risky Assets$0.003 · EV 10%

Abstract discusses Coinbase asset protection, not x402 payment finality. Off-topic.

DecideSKIP
Decrypt — Putin Signs Russia's First Crypto Law: Trading Is Legal, Payments Stay Banned$0.002 · EV 10%

News about Russian crypto regulation, not about x402 settlement latency. No relevance to the query.

DecideSKIP
CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data — Crypto Long & Short: Inside the 300-to-1 onchain gap between the dollar and euro$0.002 · EV 20%

Abstract covers onchain stablecoin gap between dollar and euro, not x402 finality timing. Not specific enough.

DecideSKIP
Inner Axiom — The Codex — The Journey of the Soul$0.002 · EV 0%

Esoteric spiritual content, completely unrelated to x402 or payments.

DecideSKIP
Conzit Labs — Tom Holland's Candid Take on Film Promotion Challenges$0.002 · EV 0%

Film promotion content, no relevance to x402 payments or settlement.

DecideSKIP
Keryx Engineering (first-party) — Recovering a Keryx paid research job$0.002 · EV 20%

First-party Keryx engineering notes on buyer recovery, not about x402 settlement latency. Not relevant to the query.

Fetch

Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)

Fetch

Reused cached Web Payments Review — How long do x402 payments take to finalize? (free) — S1

Fetch

Reused cached Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc (free) — S2

Re-evaluate

Sub-claim "How long do x402 payments take to finalize?": 90% covered by S1, S2 — Two sources provide specific timing: S1 states ~15 seconds (Ethereum L1), S2 states ~180ms median (Arc BFT). Both directly answer the question with different contexts. The answer is explicitly supported; no further detail is required by the question.

Re-evaluate

Coverage is high (0.9) with two direct answers from different contexts. The question is fully answered; no affordable skipped sources are needed.

Sufficiency

Final check — "How long do x402 payments take to finalize?": 100% assessed by S1, S2

Sufficiency

Final coverage assessment — Both sources directly answer the question about x402 payment finalization times, but they provide different answers based on different contexts (Ethereum L1 vs. Arc). The question asks for a general answer, and both sources are relevant, but they conflict. However, the instruction is to assess coverage based on what the sources explicitly state, not to resolve conflicts. The first source (S1) gives a clear answer of about 15 seconds, and the second (S2) gives a clear answer of roughly 180 milliseconds. Both are supported by their respective sources, so coverage is high for each individually. The sub-claim is fully answered by each source in its own context, so coverage is 1.0, but there is a discrepancy in the answers that is not resolved in the sources. The missing part is not about the time itself, but about reconciling the different times, which is not asked for. Therefore, coverage is 1.0 as the question is explicitly answered by both sources.

Synthesize

Synthesizing a grounded answer from 2 source(s)…

Evidence

Relevance review returned; only checked excerpts can retain support, and review cannot raise it.

Adjudicate

⚖️ Sources disagreed on Finalization time for x402 payments. — S1 About 15 seconds on Ethereum L1. vs S2 Roughly 180 milliseconds on Arc testnet. → reported preference: Both are trusted as they describe different network contexts. (The sources provide different finalization times because they refer to different networks (Ethereum L1 vs. Arc testnet). The answer reflects both contexts.)

Evidence

Verified — S1 supports claim 1 at 100%: “In our reading, an x402 payment takes about 15 seconds to settle, similar to an Ethereum L1 block time, because each payment is its own tran…”

Evidence

Verified — S2 supports claim 1 at 100%: “Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, …”

Synthesize

Drafted answer citing 2 source(s)

Verdict

Confidence: Low — 1 source disagreement remains unresolved; coverage scores do not resolve conflicting evidence.

Attribute

Web Payments Review contributed 50% → reward $0.01

Attribute

Arc Settlement Benchmarks contributed 50% → reward $0.01

Settle

Settled $0.01 citation reward → Web Payments Review (2a9ecd4e-4…)

Settle

Settled $0.01 citation reward → Arc Settlement Benchmarks (7c77b015-4…)

Done

Done. Spent $0.02 across 2 confirmed/simulated payment(s) to creators.

Read checkpoints

Read checkpoint evidence is unavailable for this report. Historical, private and unsupported native runs are not reconstructed.

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.

Manage question privacy

Recorded purchase outcomes

Did the exact article versions bought for this answer appear in its citations? This view scores retained BUY decisions against payment observations recorded in the same dispatch trace.

Recorded settlement bookkeeping only; Circle and chain settlement have not been independently rechecked here.

This is a partial retained trace sample, not a full payment ledger. An absent matching payment does not prove that no payment occurred; excluded and unconfirmed costs remain unknown.

Recorded network
eip155:5042002
Dispatch recorded at
2026-09-12T00:56:09.659Z
Frozen testnet archive, captured 2026-10-03T00:26:18.665Z. This is historical testnet evidence, separate from current mainnet activity.
Archive source commit
f9dca8d04f4657abbf0153175feec65728ba6a99
Archive database SHA-256
c5d9c0d2bf01099de526d7510321eabd1b0e3519f2792d40b61e49062d766272

Participant cohort: unknown. No outside-customer usage is inferred.

0 scored exact-version purchases from 0 recorded BUY decisions; 0 BUY decisions unscored. 2 of 2 trace payment observations excluded.

Each unique source + item + content version with positive matching recorded settled access counts once. Duplicate BUYs, missing identities, zero/unconfirmed access and incompatible payment observations cannot create a scored purchase. CACHE and SKIP decisions are outside this sample.

Exact-version citation hit rate
Unmeasured

No scored purchases; the hit rate is unmeasured.

Recorded access cost of uncited purchases
Unmeasured

Counts only scored purchases. Descriptive access cost, not causal regret or proof that the purchase was useless.

Predicted value and observed citations

Bins compare the recorded predicted value with citation occurrence in this one dispatch. Small samples do not validate a probability model.

Value bandPurchasesPredicted mean (0–1)Citation rate
0–0.20UnmeasuredUnmeasured
0.2–0.40UnmeasuredUnmeasured
0.4–0.60UnmeasuredUnmeasured
0.6–0.80UnmeasuredUnmeasured
0.8–10UnmeasuredUnmeasured

Missed value, cost per supported claim, budget alternatives and counterfactual outcomes are unmeasured. No extra reading or learning was performed.

A new follow-up runs on Arc mainnet with today’s sources and budget. Only the historical question supplies context.

Ask a follow-upNew dispatch · creators paid again

Carries this dispatch’s question as context — never its answer. The next dispatch is read from sources bought for it.

From the archive

Related dispatches