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

Identified 4 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 4/4 positive proposal(s): 4 cached + 0 fresh, predicting 4/4 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 (4/4); 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

Reused cached Stablecoin Ledger — Why USDC settles instantly onchain (free) — S4

Attention budget is full at 4 source(s); no broader context will be purchased.

Final check — "What is the definition or scope of x402 payments?": 100% assessed by S2

Final check — "What is the typical finalization time for x402 payments?": 90% assessed by S1, S3

Final check — "What factors commonly affect the finalization time of x402 p…": 60% assessed by S1, S3

Final check — "How do finalization times for x402 payments vary in differen…": 50% assessed by S1, S3

Final coverage assessment — S1 directly answers the core finalization-time question for x402 batched settlements on Arc (median 178ms, p95 240ms, sub-second finality). S2 defines x402 as an HTTP 402-based payment rail, covering the definition/scope sub-claim. S3 provides a conflicting typical finalization estimate (~15 seconds, Ethereum L1-like) and attributes it to per-transaction mining, which partially addresses typical time and factors. S4 discusses USDC settlement generally but does not mention x402, so it does not answer any x402-specific sub-claim. The requested variation across different systems/contexts is only partially covered: S1 gives Arc/Gateway-batched context and S3 gives an Ethereum L1-style context, but no systematic comparison or other systems are supplied. The assessment does not establish a complete supported answer for every requested part.

Synthesizing a grounded answer from 4 source(s)…

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

⚖️ Sources disagreed on Typical x402 payment finalization time — S1 x402 batched settlements on Arc testnet finalize in roughly 180 milliseconds (median 178ms, p95 240ms), with sub-second finality. vs S3 An x402 payment takes about 15 seconds to settle, similar to Ethereum L1 block time, because each payment is its own transaction waiting to be mined. → reported preference: S1 (S1 provides specific measured benchmarks (median 178ms, p95 240ms) from thousands of submitBatch calls on Arc testnet and explains the mechanism (BFT consensus, Gateway batching, not block-time-bound), making it more specific and internally consistent than S3's unsourced 'reading' estimate.)

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

Verified — S2 supports claim 1 at 80%: “A server responds 402 with machine-readable payment requirements; the client signs a payment authorization and retries.”

Verified — S1 supports claim 2 at 100%: “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 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…”

Verified — S1 supports claim 3 at 70%: “Arc's BFT consensus delivers sub-second finality, so a Gateway-batched payment confirms in well under a quarter second — it is not block-tim…”

Verified — S3 supports claim 3 at 80%: “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…”

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

Verified — S3 supports claim 4 at 80%: “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…”

Below reward gate — S4 supports claim 4 at 20%: “USDC is a fully-reserved dollar stablecoin that settles peer-to-peer onchain in seconds.”

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

Drafted answer citing 3 source(s)

Confidence: Low — the final assessment does not establish a complete supported answer for every requested part.

Arc Settlement Benchmarks contributed 40% → reward $0.008

Agent Economy Weekly contributed 20% → reward $0.004

Web Payments Review contributed 40% → reward $0.008

Settled $0.008 citation reward → Arc Settlement Benchmarks (bdf5b972-1…)

Settled $0.004 citation reward → Agent Economy Weekly (d1b1e533-0…)

Settled $0.008 citation reward → Web Payments Review (ed9821ff-c…)

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