intel.hugen.tokyo/intel/token-report/lite
1.Catalog declaration
| Resource URL | https://intel.hugen.tokyo/intel/token-report/lite |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x29322ea7ecb34aa6164cb2ddeb9ce650902e4f60 |
| Declared price (base units) | 20000 |
| Catalog status | active |
| First seen / last seen | 2026-08-17 01:06 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 698 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 611 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 675 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 729 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 838 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 683 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 645 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 773 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 845 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 707 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 1138 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 788 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 761 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 839 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 706 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 915 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 757 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 761 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 700 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 777 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 863 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 656 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 641 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 704 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 925 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 725 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 720 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 1042 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 746 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 805 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 09-23 00:022026-09-23 00:02 UTC | settled (nonce-bound) | 200 | 0x7a23d784…f52e | 3632 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-12 00:022026-09-12 00:02 UTC | settled (nonce-bound) | 200 | 0x7b49f159…1d7c | 2175 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-03 12:092026-09-03 12:09 UTC | settled (amount + payee) | 200 | 0x39978f3f…1976 | 2051 ms |
| 20000 units (≈ $0.02 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/62e15853-bbe8-4e49-8979-e2f5b9bb592b)4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.