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

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/4 positive proposal(s): 3 cached + 0 fresh, predicting 2/2 claim(s) above the evidence floor with $0.000000/$0.020000 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 spend wallet ready: 0x29028Fe1122E17Fe7863A22701e863FE4DaE1aFB (balance sufficient)

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

Reused cached Agent Economy Weekly — x402 turns HTTP 402 into an agent payment rail (free) — S2

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

Sub-claim "What are x402 payments?": 80% covered by S2 — Source S2 explicitly describes x402 payments as reviving the HTTP 402 'Payment Required' status as a payment rail, where a server responds with payment requirements and the client signs authorization. This provides a direct answer to what x402 payments are.

Sub-claim "How long do x402 payments take to finalize?": 60% covered by S1, S3 — S1 reports x402 batched settlements on Arc testnet finalize in roughly 180ms (median 178ms, p95 240ms). S3 states an x402 payment takes about 15 seconds to settle, similar to Ethereum L1 block time. These sources provide conflicting answers, but both address the question. The coverage is partial because the sources disagree on finality time, suggesting context-dependence (e.g., Arc vs. Ethereum L1) that is not fully reconciled.

Coverage for the main question is adequate at 0.6 due to conflicting sources, but both sources directly address finality time. No skipped sources appear relevant to resolving the conflict or adding critical missing information within the budget.

Final check — "What are x402 payments?": 100% assessed by S2

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

Final coverage assessment — The question asks about the finalization time for x402 payments. Source S1 provides a direct measurement of finalization time (~180ms median) for x402 batched settlements on Arc testnet. Source S2 provides context on what x402 payments are (reviving HTTP 402 as a payment rail) but does not address finalization time. Source S3 provides a conflicting estimate (about 15 seconds, similar to Ethereum L1 block time) but it is an opinion ('In our reading') and is not a measured benchmark. Since the question asks 'How long do x402 payments take to finalize?', it requires an answer about finalization time, and S1 provides a direct, measured answer. S2 provides the definition needed for the first sub-claim. The finalization time is directly answered by S1, with S3 offering an alternative view but not directly supported as a fact. There is no missing requested part; the question is fully answered by the combination of S1 and S2.

Synthesizing a grounded answer from 3 source(s)…

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

⚖️ Sources disagreed on Finalization time for x402 payments — S1 Finalizes in roughly 180 milliseconds on Arc testnet vs S3 Takes about 15 seconds to settle, similar to Ethereum L1 block time → reported preference: S1 (The claim from S1 is based on specific, measured benchmark data ('measured median 178ms, p95 240ms'), whereas S3 presents a generalized opinion ('In our reading') without citing measurement data. The S1 source also specifies a particular implementation context (Arc testnet), making its claim more precise and verifiable.)

Verified — S2 supports claim 1 at 70%: “x402 revives the dormant HTTP 402 'Payment Required' status as a real payment rail.”

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

Verified — S3 supports claim 2 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…”

Drafted answer citing 3 source(s)

Confidence: Moderate — source preferences are explained, but conflicting evidence limits confidence.

Arc Settlement Benchmarks contributed 50% → reward $0.01

Agent Economy Weekly contributed 10% → reward $0.002

Web Payments Review contributed 40% → reward $0.008

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

Settled $0.002 citation reward → Agent Economy Weekly (d3f05203-e…)

Settled $0.008 citation reward → Web Payments Review (8bb1ec41-a…)

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