Archived dispatch

How long do x402 payments take to finalize?

Lowconfidence1 sub-claim remains below the evidence threshold

9/18/2026, 2:36:36 PM · llm:mimo:mimo-v2.5

The dispatch, itemised.

§ IThe decision$0.02 / $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/4 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
Arc Settlement Benchmarks — Measuring x402 settlement latency on Arc$0.003 · EV 85%

Directly addresses the question with measured x402 settlement latency on Arc testnet. Cached and free. Best candidate for finalization time data. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).

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

Title exactly matches the question, covers end-to-end settlement timing for x402. Cached and free. Provides broader commentary on similar payment rails. — selected for the claim-aware evidence portfolio (targets claim 1; 0 fetch USDC, 1 attention slot).

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

Agent Economy Weekly covers x402 standard as a payment rail, likely to mention settlement timing. Strong reputation on subject. Cached and free. — 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
Stablecoin Ledger — Why USDC settles instantly onchain$0.003 · EV 50%

Stablecoin Ledger discusses USDC settlement speed ('seconds with finality'), relevant to x402 finalization if using USDC. Cached and free. — 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
The Coinbase Blog - Medium — Real-time reconciliation with Overseer$0.003 · EV 20%

Coinbase Blog on reconciliation doesn't address x402 finalization time directly. Cached but low relevance despite stablecoin tag.

DecideSKIP
Stripe Blog — Solo founding is at an all-time high: Top performers have these traits in common$0.002 · EV 15%

Stripe Blog article is about solo founders, not x402 settlement timing. Cached but not relevant despite Stripe's payment expertise.

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

Cointelegraph article is about crypto payments adoption among merchants, not x402 finalization time. Cached but tangential.

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

Decrypt article is about Russia's crypto law, not x402 settlement timing. Cached but not relevant.

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%

CoinDesk article is about dollar vs euro stablecoin adoption, not x402 finalization time. Cached but tangential.

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

Onchain Micropayments Digest covers nanopayment floor, not x402 finalization time. Cached but not directly relevant.

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

Distributed Systems Notes on idempotency keys don't address x402 finalization time. Cached but not relevant.

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

Retro Game Hardware is completely off-topic. Cached but no relevance.

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

Inner Axiom is esoteric content, completely off-topic. Not cached, skip.

DecideSKIP
Conzit Labs — Real-Time Gesture Controlled Invisibility Cloak in Python (MediaPipe & OpenCV)$0.002 · EV 0%

Conzit Labs article is about computer vision, completely off-topic. Cached but no relevance.

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

Simon Willison's Weblog is about AI model adoption, not x402 payments. Not cached, low relevance.

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

Hugging Face Blog is about AI tutors, not x402 payments. Not cached, no relevance.

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

Vitalik Buterin's website is about DeFi, not x402 finalization time. Not cached, tangential at best.

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

Keryx Engineering first-party notes on buyer recovery might reference x402 payment mechanics. Cached and free. Has tags for x402 and settlement. — cached bytes are free, but this read does not clear the attention gate (EV 0.40, minimum 0.45, with a required claim target).

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

Latent.Space is about AI ontologies, not x402 payments. Cached but not relevant.

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

Garden & Soil Monthly is about gardening, completely off-topic. Cached but no relevance.

Fetch

Agent spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)

Fetch

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

Fetch

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

Re-evaluate

Sub-claim "What is the finalization time for x402 payments as implement…": 0% covered — The gathered sources discuss x402 finalization times in general contexts: S1 mentions Arc testnet batched settlements finalizing in ~180ms, and S2 mentions about 15 seconds similar to Ethereum L1 block time. Neither source specifically addresses Keryx's implementation of x402 payments. There is no information about Keryx's specific finalization time.

Re-evaluate

The sub-claim specifically asks about Keryx's implementation, but none of the gathered sources provide this information. The skipped source 'Keryx Engineering (first-party) — Recovering a Keryx paid research job' is the most relevant as it's directly from Keryx and might contain details about their payment implementation, including finalization times. This source costs 0.002, which fits within the remaining budget of 0.02. Other skipped sources are not relevant to Keryx's specific implementation.

Re-evaluate

Filling gap — buying Keryx Engineering (first-party) — Recovering a Keryx paid research job ($0.002)…

Re-evaluate

Paid $0.002 to Keryx Engineering (first-party) — Recovering a Keryx paid research job (settled 36844cf0-9…) — S3

Sufficiency

Final check — "What is the finalization time for x402 payments as implement…": 0% assessed

Sufficiency

Final coverage assessment — The user asks for finalization time of x402 payments as implemented by Keryx. The gathered sources include a general benchmark on Arc testnet (S1) showing ~180ms finality, a general review (S2) claiming ~15 seconds (Ethereum L1 time), and a Keryx-specific document (S3) that is excerpted but contains only introductory text about recovery, not finalization time. No source explicitly states Keryx's finalization time. S1 and S2 are not Keryx-specific. Therefore, the sub-claim lacks direct support. The assessment does not establish a complete supported answer for every requested part.

Synthesize

Synthesizing a grounded answer from 3 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 Roughly 180 milliseconds on Arc testnet. vs S2 About 15 seconds, similar to Ethereum L1 block time. → reported preference: S1 (S1 provides specific, measured performance data from a testnet deployment of a BFT consensus system, while S2 presents a general comparison to Ethereum L1 without citing implementation details. The context in S1 is more specific to a particular x402 implementation.)

Evidence

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

Evidence

Verified — S2 supports claim 1 at 50%: “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

Rejected 0 invalid evidence span(s) and 1 unsupported citation marker(s); rejected markers cannot receive citation rewards.

Synthesize

Drafted answer citing 2 source(s)

Verdict

Confidence: Low — 1 sub-claim remains below the evidence threshold.

Attribute

Arc Settlement Benchmarks contributed 50% → reward $0.01

Attribute

Web Payments Review contributed 50% → reward $0.01

Settle

Settled $0.01 citation reward → Arc Settlement Benchmarks (f033a340-1…)

Settle

Settled $0.01 citation reward → Web Payments Review (c6b676c3-5…)

Done

Done. Spent $0.022 across 3 confirmed/simulated payment(s) to creators.

§ IIIThe settlementweighted · USDC on Arc
50%
50%
1

Arc Settlement Benchmarks

batched

50%$0.01
2

Web Payments Review

batched

50%$0.01
§ IIThe reading2 cited
Lowconfidence1 sub-claim remains below the evidence thresholddeep researchpreview plan 1/1 claimsportfolio 2/4 · evidence 100%

> ⚠ Low confidence — 1 sub-claim remains below the evidence threshold within budget. Treat this as provisional.

The finalization time for x402 payments depends on the settlement platform. On Arc's testnet, batched x402 settlements finalize in roughly 180 milliseconds (median 178ms, p95 240ms) . However, other implementations may use different blockchains; for instance, one view describes an x402 payment taking about 15 seconds to settle, similar to an Ethereum L1 block time . The Keryx source does not provide information on payment finalization times, as it focuses on a recovery process.

Evidence ledger — quotes verified before rewards

  1. What is the finalization time for x402 payments as implemented by Keryx?

    0%
    Across thousands of submitBatch calls on Arc testnet, x402 batched settlements finalize in roughly 180 milliseconds (measured median 178ms, p95 240ms). [S1] Measuring x402 settlement latency on Arc
    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. [S2] How long do x402 payments take to finalize?

Footnotes — each one pays its author

Helpful?
Spent$0.022
To creators100%
Decisions0 bought · 2 cached · 18 skipped
llm:mimo:mimo-v2.5

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

2 exact cited article versions still match Keryx's current index.

Inspect machine-readable audit

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