mcpfax-intel.bowling-anthony.workers.dev
9 routes listed in Coinbase Bazaar pay into 0x1831f336585a6c67b6a954d28f3e07f44c4eebbd, a wallet shared by 7 hosts, so the figures below cover all of them.
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.
Who paid
| Payer class | Wallets | Payments | USDC | What it means |
|---|---|---|---|---|
| Repeat payers, no flag | 0 | 0 | $0 | Paid this wallet two or more times and carries none of the flags below. |
| One-payment wallets | 0 | 0 | $0 | Paid this wallet once in the window and carries none of the flags below. |
| Wallets paying 10+ sellers | 2 | 4 | $0.024 | Paid 10 or more listed sellers in the window. Catalog crawlers, monitors and scouts behave this way; so do some busy agents. |
| Campaign wallets | 0 | 0 | $0 | Also pays a known campaign in the window, where participants pay per run for points or prizes, and paid fewer than ten sellers. |
| Seller-linked wallets | 0 | 0 | $0 | Received USDC from this seller's wallet in the window, or is one of the seller's own listed wallets. |
Payments per day
011-07
011-08
011-09
011-10
011-11
411-12
0
What Bazaar reports
33 calls over 30 days across this wallet's routes, and up to 9 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.5 days left unless it is paid again.
Listed prices: $0.005, $0.006, $0.01.
Is this your API?
The free Bazaar check shows whether a buyer's agent can find it for a task, and what to fix.
Hosts paying into this wallet
mcpfax-markets.bowling-anthony.workers.dev, faultcode-diagnostic-mcp.bowling-anthony.workers.dev, feed-reader.bowling-anthony.workers.dev, mcpfax-intel.bowling-anthony.workers.dev, mcpfax-reliability.bowling-anthony.workers.dev, mcpfax-utility.bowling-anthony.workers.dev, onchain-toolkit.bowling-anthony.workers.dev
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?host=mcpfax-intel.bowling-anthony.workers.dev (0.02 USDC on Base over x402)