Weekly statistic · tracked catalog

How many distinct buyers paid x402 sellers this week?

2,514¹ cite distinct sender addresses paid tracked sellers at least once, making 172,067¹ cite verified payments — in the week 2026-10-05 → 2026-10-11 (Monday–Sunday UTC), computed 2026-10-13 from the on-chain record through block 52,544,868³ cite .

Updated weekly · data as of 2026-10-13 · window 2026-10-05–2026-10-11 · method score-v1.0.0 · tracked-catalog data · methodology

Compared with the prior week

2,514² cite distinct buyers this week vs 3,697² cite the prior week ( −32.0%² cite ) — a distinct count over each seven-day window, not a sum of days. Prior week: 2026-09-28 → 2026-10-04, all seven days coverage-published.

The underlying numbers

Dollar figures print to the cent; the exact integer micro-USDC values, the full provenance (flags version, block bounds, coverage, catalog size) and earlier windows are in /api/v1/stats/weekly/unique-buyers-this-week.

What this measures

Distinct sender addresses that made at least one verified payment to a tracked seller address during one closed Monday–Sunday UTC week, after the real-buyer exclusions: senders flagged exchange, fan-out, or self are removed, and self-transfers do not count. The payment count for the same week sits beside it, and the payments-per-buyer line gives a first hint of concentration.

A buyer here is an address, not a person or an agent: one agent can pay from many wallets and many agents can share one, so this number bounds neither. It is a distinct count over the whole week — not the sum of the per-day “real buyers” figures on the market dashboard — and the prior week therefore compares window to window, both seven days.

Reading this number honestly

Scope. This is a tracked-catalog figure: USDC received on Base by the seller addresses our x402 Bazaar-derived catalog tracks — never “the x402 market,” never “the agent economy’s volume.” Wallets can receive USDC for reasons unrelated to x402 sales; the method removes only known exchange, fan-out, and self flows.

What “verified” means here. “Verified” is the payment-level predicate of score-v1.0.0: a payment at or above the dust floor of $0.01 cite , sender not flagged exchange, fan-out, or self, not a self-transfer. It is not the seller-level “verified tier” on the rankings; the two labels are never conflated. Methodology: verified revenue

Dust. Payments below the floor are counted and summed separately and shown beside verified — never netted out, never labeled verified. The dust figures for the same week are on How much x402 traffic is dust?

1. Every USDC transfer on Base to a tracked catalog address in the window, passed through the score-v1.0.0 verified predicate (at or above the dust floor, sender not flagged exchange/fan-out/self, not a self-transfer). Recomputed weekly from the warehouse by the frozen method; buyer flags at version flags-2026-10-13. Methodology: verified revenue
2. The prior week is the closed Monday–Sunday UTC week immediately before, by the same method and the same flags version. Comparisons print as daily rates where the quantity sums over days; distinct counts compare window to window (both seven days). A future flags bump can revise past weeks, visibly — rows are append-only.
3. Coverage at compute: all seven window days coverage-published at coverage_ratio 1.00; the window recompute reconciles to the micro with the published v_market_daily weekly sum. On-chain record observed through block 52,544,868 (2026-10-13T08:11:23.000Z); window blocks 52,184,527–52,486,926; chain-sync last success 2026-10-13T08:21:07.381Z; 2,088 tracked seller addresses, 1,292 of 1,292 tier-A complete.

Computed from on-chain USDC transfers on Base by the published method; claimed figures are never used. Full methodology · Machine-readable: /api/v1/stats/weekly/unique-buyers-this-week · all eight: /stats (/api/v1/stats/weekly)