0x1b258d4962e2a0103e932c155a3b9efcac40964a
4 routes listed in Coinbase Bazaar pay into 0x1b258d4962e2a0103e932c155a3b9efcac40964a.
Last 7 UTC days (2026-11-06 to 2026-11-12), read to 2026-11-12 00:59:40 UTC. This wallet has been read for 6.04 of those days.
What Bazaar reports
4 calls over 30 days across this wallet's routes, and up to 1 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 21.4 days left unless it is paid again.
Listed prices: $0.05, $0.06.
Is this your API?
The free Bazaar check shows whether a buyer's agent can find it for a task, and what to fix.
How this is counted
- Sellers are the receiving wallets of every Base USDC route in Coinbase Bazaar's public catalog, re-read several times a day.
- A payment is a USDC transfer on Base into one of those wallets that used the payer's signed EIP-3009 authorization, the way x402 pays. Ordinary transfers and mints into the wallet are totalled apart. Everything is read from public RPC and bucketed by UTC day.
- Each payer gets one class per seller, in this order: seller-linked, paying ten or more sellers, campaign, then repeat or one-payment.
What this cannot tell you
- A payment here is a USDC transfer on Base that used the payer's signed EIP-3009 authorization, the way x402 pays. It is not proof that an HTTP 402 request caused it.
- Ordinary USDC transfers into the wallet are totalled apart and never counted as payments.
- A wallet with no flag is not proof of an independent customer: one operator can use many wallets.
- Funding is checked one hop only: USDC sent directly from the seller's wallet to a payer.
- Only wallets listed in Coinbase Bazaar with a Base USDC price are read.
Same data as JSON · Paid verdict with a grade, the ten largest payers and the market rank: GET /api/x402/seller-verdict?wallet=0x1b258d4962e2a0103e932c155a3b9efcac40964a (0.02 USDC on Base over x402)