https://visual.hugen.tokyo
- Payment address
- 0x29322ea7ecb34aa6164cb2ddeb9ce650902e4f60 ↗
- Network
- eip155:8453
- Subject id
- sub_01ade1a34865585a
- Indexed from
- bazaar
- First seen
- 2026-09-07
- Last seen
- 2026-09-22
What the402 says
Verdict
Not yet verifiedthe402 has not made a statement about this endpoint. Unknown is not a score.
- Level
- Indexed (level 0)
- Confidence
- 0%
- Issued
- 2026-09-21 20:09 UTC
- Expires
- 2026-09-28 20:09 UTC
- Anchored day
- 2026-09-21
Verify this signature
- Signer
- 0xB1b469776943dAeE4b1CDd448C731ac2E404d4B4
- Digest
- 0x2c24590bc8557264235b625a7c98bb352baf6bb3e2723f1a69069e13e6ab1213
- Signature
- 0x51331e66954339a96dcd1e739c260b365cc775aa971c48d1062d4e53d75148f22bcb44d743ddb76fc3a00621c1d394e185eb4d9d40268eefae31a6cbfbc017621c
Verify with recoverTypedDataAddress(typed_data, signature) === signer.
{
"domain": {
"name": "the402 Trust",
"version": "1",
"chainId": 8453
},
"primaryType": "Verdict",
"types": {
"Verdict": [
{
"name": "subjectKey",
"type": "bytes32"
},
{
"name": "verdict",
"type": "string"
},
{
"name": "level",
"type": "uint8"
},
{
"name": "confidenceBps",
"type": "uint16"
},
{
"name": "evidenceRoot",
"type": "bytes32"
},
{
"name": "issuedAt",
"type": "uint64"
},
{
"name": "expiresAt",
"type": "uint64"
},
{
"name": "methodology",
"type": "string"
}
]
},
"message": {
"subjectKey": "0x3201adf11bb1c1fd2ecc35d022d934e08afb2ba1b6d81bcf1be6b1d0728c631e",
"verdict": "unknown",
"level": 0,
"confidenceBps": 0,
"evidenceRoot": "0x2c6b445c0dcd621ec102fb440c5c8885c48c01f2ee5072af964495dcadef7219",
"issuedAt": "1790021384",
"expiresAt": "1790626184",
"methodology": "the402-trust-v1"
}
} Evidence
Dimensions
A dash is a dimension the402 has not measured — not a zero.
Evidence
| Source | Observations |
|---|---|
| chain | 14 |
- Evidence root
- 0x2c6b445c0dcd621ec102fb440c5c8885c48c01f2ee5072af964495dcadef7219 ↗
- Methodology
- the402-trust-v1 · machine-readable version ↗
The evidence file is content-addressed and served whether or not the public read API is on: an on-chain pointer has to resolve. The counts above say how much the402 has seen and where it came from. They do not add up to the verdict on their own: the weights, the decay steps and the thresholds behind it are not published, and the methodology page says so and says why.
Statement history
Every statement the402 has made about this endpoint, newest first.
Paid probes
the402 pays for no probes. Every one of these was funded by this endpoint's own claimant, by a buyer verifying it, or from the dispute pool — and it only runs for an endpoint whose operator claimed it and opted in. Requests are published in full; responses as a hash and a redacted excerpt, with whether the answer passed.
No paid probes yet
the402's API answered and has no paid probes to report here. That is a fact about this record, not a gap in the page.
Chain activity
| Day | Payments | Payers | Volume |
|---|---|---|---|
| 2026-09-21 | 34 | 29 | $0.21 |
| 2026-09-20 | 19 | 18 | $0.29 |
| 2026-09-19 | 19 | 19 | $0.10 |
| 2026-09-18 | 23 | 23 | $0.12 |
| 2026-09-17 | 29 | 22 | $0.20 |
| 2026-09-16 | 34 | 26 | $0.24 |
| 2026-09-15 | 43 | 13 | $0.50 |
| 2026-09-14 | 22 | 11 | $0.18 |
| 2026-09-13 | 17 | 17 | $0.29 |
| 2026-09-12 | 34 | 18 | $0.28 |
| 2026-09-11 | 17 | 16 | $0.12 |
| 2026-09-10 | 31 | 21 | $0.17 |
| 2026-09-09 | 40 | 19 | $0.26 |
| 2026-09-08 | 50 | 35 | $0.28 |
| 2026-09-07 | 24 | 15 | $0.13 |
| When | From | Amount | Transaction |
|---|---|---|---|
| 2026-09-22 07:29 UTC | 0x926b50888d99057a163e4e29005a62a3bd4d1eaa | $0.0050 | 0xb163eb2f73… ↗ |
| 2026-09-22 07:27 UTC | 0x4bfb37fb4000b90936ce5a7adbd96a48f0fd4430 | $0.0050 | 0xa838104c26… ↗ |
| 2026-09-22 06:23 UTC | 0x54e163e9b8edda194d83f46add921bfa5fc5f4e0 | $0.0100 | 0xc1fe1553f4… ↗ |
| 2026-09-22 06:03 UTC | 0x54e163e9b8edda194d83f46add921bfa5fc5f4e0 | $0.0050 | 0xa9c6452794… ↗ |
| 2026-09-22 05:54 UTC | 0xeeef0a5b1f26ecc82dad66e6795c682fe818a5e7 | $0.0050 | 0xe4027e64dc… ↗ |
| 2026-09-22 05:54 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0500 | 0x4bfa46daff… ↗ |
| 2026-09-22 05:54 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0200 | 0x02fe495d48… ↗ |
| 2026-09-22 05:53 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0100 | 0x5a51423564… ↗ |
| 2026-09-22 05:52 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0050 | 0x4f57a73d6e… ↗ |
| 2026-09-22 05:51 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0100 | 0xc230b303dc… ↗ |
| 2026-09-22 05:51 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0100 | 0x347f154a18… ↗ |
| 2026-09-22 05:51 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0100 | 0xc55cc977a7… ↗ |
| 2026-09-22 05:51 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0200 | 0x7092ab05c8… ↗ |
| 2026-09-22 05:51 UTC | 0xb13eb9a5a650d86a0f173f8300ba28d281e5a6ce | $0.0200 | 0x5f5a9ee160… ↗ |
| 2026-09-22 05:44 UTC | 0x82d598d7afbe04204213a242be74b059c07f41a9 | $0.0050 | 0x85818c93e8… ↗ |
| 2026-09-22 03:35 UTC | 0xb782a5579167af73eb292fbb703ff4dd88e1a209 | $0.0050 | 0x40bec0b485… ↗ |
| 2026-09-21 23:47 UTC | 0x60a5173dc4c5601a8f639b78fbcddcaa02f85cfb | $0.0050 | 0x6a08c68443… ↗ |
| 2026-09-21 23:42 UTC | 0x8dba0168c4243465292397b4ba238dbf559b947f | $0.0050 | 0xc0146910d1… ↗ |
| 2026-09-21 23:35 UTC | 0x12b9b944c2b28948a94a76560267fd0eded8f338 | $0.0050 | 0xf7dca356a0… ↗ |
| 2026-09-21 23:26 UTC | 0x12b9b944c2b28948a94a76560267fd0eded8f338 | $0.0050 | 0xe86c2f425c… ↗ |
the402's index has read to block 51637358 (2026-09-22 08:01 UTC), 0 behind head.
USDC Transfer events to this payTo on eip155:8453, indexed by the402 from the public chain. `window_30d` is the trailing 30-day stamp, recomputed nightly (it can lag `recent` by up to a day; null until an inbound transfer has been seen); `recent` and the flags come from the 90-day raw log, `daily` is permanent; `coverage` says how far the index has read. Wallet-level: a payTo fronting several endpoints shows the same figures on each. Payer addresses are public chain data and are never joined to a participant name.
Risk flags
{
"window_days": 30,
"basis": "ratios over transfers indexed to watched payTos",
"raise_ratio": 0.8,
"keep_ratio": 0.7,
"pairs": [
{
"payer": "0x2c42e6873824541cc0ddf826dd0baf6836e81395",
"pair_txns": 21,
"payer_ratio": 1,
"payee_ratio": 0.09
},
{
"payer": "0x952a635148374f916f777816fc5459048abf9ff8",
"pair_txns": 3,
"payer_ratio": 1,
"payee_ratio": 0.01
},
{
"payer": "0xfaa391609ad159fbc535ea2c413e634179eec914",
"pair_txns": 3,
"payer_ratio": 1,
"payee_ratio": 0.01
}
]
}Flags are patterns the402 detected on public chain data. A claimant can contest one through the dispute register, and an upheld contest resolves it for good.
Disputes
No disputes yet
the402's API answered and has no disputes to report here. That is a fact about this record, not a gap in the page.
Advertised resources
| Resource | Method | x402 | Declared price | Source |
|---|---|---|---|---|
| https://visual.hugen.tokyo/visual/ocr | GET | v2 | 50000 | bazaar |
| https://visual.hugen.tokyo/visual/parse | GET | v2 | 20000 | bazaar |
| https://visual.hugen.tokyo/visual/pdf | GET | v2 | 20000 | bazaar |
| https://visual.hugen.tokyo/visual/screenshot | GET | v2 | 20000 | bazaar |
Is this your endpoint?
Claiming it proves you control it — through your own origin, your DNS, or the key you are paid at — and turns on the settings only an operator should have: opting into paid probes you fund, the sandbox, and contesting anything here you think is wrong. How claiming works →
Bought from this endpoint and want the outcome on the record? A signed attestation naming the payment transaction is evidence the402 weighs. How to report an outcome →
Live Claiming and attestation intake are open on the402's public trust API. What a fixture snapshot renders is a record; the switches it describes are production's.