x402 payer ledger

api.onesource.io

70 routes listed in Coinbase Bazaar pay into 0x52e29e0d2aa49bfbfc548c0a9f2196f4aa51f3ea.

Last 7 UTC days (2026-11-06 to 2026-11-12), read to 2026-11-12 00:49:27 UTC. This wallet has been read for 6.03 of those days.

510 of 571 paying wallets came back and carry no flag.
4,609payments
$37.52USDC paid
571paying wallets
510repeat payers with no flag
<1%of payments from the largest payer

Who paid

Payer classWalletsPaymentsUSDCWhat it means
Repeat payers, no flag5104,450$36.74Paid this wallet two or more times and carries none of the flags below.
One-payment wallets4848$0.167Paid this wallet once in the window and carries none of the flags below.
Wallets paying 10+ sellers12110$0.618Paid 10 or more listed sellers in the window. Catalog crawlers, monitors and scouts behave this way; so do some busy agents.
Campaign wallets11$0.003Also pays a known campaign in the window, where participants pay per run for points or prizes, and paid fewer than ten sellers.
Seller-linked wallets00$0Received USDC from this seller's wallet in the window, or is one of the seller's own listed wallets.

Payments per day

11-06
824
11-07
676
11-08
675
11-09
466
11-10
998
11-11
933
11-12
37

What Bazaar reports

16,045 calls over 30 days across this wallet's routes, and up to 735 unique payers on one route.

Routes appear to leave Bazaar's catalog 30 days after their last paid call: none older was listed when we checked. On that basis the most recently paid route here has about 29.6 days left unless it is paid again.

Listed prices: $0.001, $0.003, $0.004, $0.005, $0.008, $0.01, $0.02, $0.05.

Is this your API?

The free Bazaar check shows whether a buyer's agent can find it for a task, and what to fix.

Run the free Bazaar check

How this is counted

What this cannot tell you

Same data as JSON · Paid verdict with a grade, the ten largest payers and the market rank: GET /api/x402/seller-verdict?host=api.onesource.io (0.02 USDC on Base over x402)