fiatdock.com
7 routes listed in Coinbase Bazaar pay into 0x0ce1c00d5164952019ed5b923f9a58ab2e96a4e9, a wallet shared by 2 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:49:27 UTC. This wallet has been read for 6.03 of those days.
Who paid
| Payer class | Wallets | Payments | USDC | What it means |
|---|---|---|---|---|
| Repeat payers, no flag | 1 | 7 | $7.00 | 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 | 1 | 1 | $0.01 | 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 | 1 | 217 | $9.10 | Received USDC from this seller's wallet in the window, or is one of the seller's own listed wallets. |
Payments per day
911-07
611-08
10011-09
4511-10
6211-11
311-12
0
What Bazaar reports
37 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 28.8 days left unless it is paid again.
Listed prices: $0.01, $0.25, $0.5, $1, $2.
Is this your API?
The free Bazaar check shows whether a buyer's agent can find it for a task, and what to fix.
Other wallets this host uses
| Wallet | Payments | USDC | Payers | Repeat payers, no flag |
|---|---|---|---|---|
| 0xeb12bb2f52eed33dba6a00774e48324032fd87c6 | 68 | $0.1505 | 5 | 1 |
| 0xfe257ef6dc89f5b688ac52ef3eb8648c629fa9c4 | 19 | $0.087 | 2 | 1 |
| 0x48cda0da34816db1f997c3d3b167a4f6af850cb2 | 4 | $0.04 | 2 | 0 |
| 0x45cc2b3a354d4e9da2eb14189c5bbe6394c1efb6 | 1 | $0.005 | 1 | 0 |
| 0xdbbc87e7947201eacc9a7521dda4801e99994566 | 1 | $0.05 | 1 | 0 |
| 0x3903f05a17676566958b0a3e0c21e0bd49b66ea0 | 0 | $0 | 0 | 0 |
| 0xf16f0882de08315b438e9f3a2abfb2d2e5d94eca | 0 | $0 | 0 | 0 |
| 0x7cc5ab4543372a6556c16c6f01e829c537f31871 | 0 | $0 | 0 | 0 |
| 0x2d42f48d8dabd263dfca580480f41316fc3110db | 0 | $0 | 0 | 0 |
| 0x02752dd743fb1cf5439f36c073cf4cbefb1d25a6 | 0 | $0 | 0 | 0 |
| 0xa5d64282e8622a2bad0855821c9d1a68c5c36cd4 | 0 | $0 | 0 | 0 |
| 0xba118ddbc65c385378f8208dd8b2420101dbfbf7 | 0 | $0 | 0 | 0 |
Hosts paying into this wallet
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=fiatdock.com (0.02 USDC on Base over x402)