content.hugen.tokyo
26 routes listed in Coinbase Bazaar pay into 0x29322ea7ecb34aa6164cb2ddeb9ce650902e4f60, a wallet shared by 11 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 | 7 | 52 | $0.49 | Paid this wallet two or more times and carries none of the flags below. |
| One-payment wallets | 67 | 67 | $0.34 | Paid this wallet once in the window and carries none of the flags below. |
| Wallets paying 10+ sellers | 10 | 29 | $0.23 | Paid 10 or more listed sellers in the window. Catalog crawlers, monitors and scouts behave this way; so do some busy agents. |
| Campaign wallets | 1 | 1 | $0.005 | 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
1111-07
3311-08
1311-09
3811-10
2211-11
3111-12
1
What Bazaar reports
617 calls over 30 days across this wallet's routes, and up to 124 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.7 days left unless it is paid again.
Listed prices: $0.005, $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.
Hosts paying into this wallet
defi.hugen.tokyo, gotobi.hugen.tokyo, scout.hugen.tokyo, tick.hugen.tokyo, visual.hugen.tokyo, mailcheck.hugen.tokyo, weather.hugen.tokyo, api.aidress.ai, content.hugen.tokyo, domain.hugen.tokyo, intel.hugen.tokyo
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=content.hugen.tokyo (0.02 USDC on Base over x402)