lionx402.com/api/x402/token-risk-indicators-json
1.Catalog declaration
| Resource URL | https://lionx402.com/api/x402/token-risk-indicators-json |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x68e3e7822cf83c824cf9606ec999b5e8a93c85b5 |
| Declared price (base units) | 30000 |
| Catalog status | delisted (since 2026-09-27 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-26 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 16:40 UTC | GET | pass | 402 | 365 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 7051 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 2173 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 920 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 8034 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 2305 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 2400 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 452 ms | — |
| 2026-09-19 22:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-09-17 04:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 302 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 318 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 655 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 645 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 439 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 8041 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 430 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 5720 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 466 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 328 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 423 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 524 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 373 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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.
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-06 12:092026-09-06 12:09 UTC | settled (nonce-bound) | 200 | 0xab6387bc…ea4d | 1335 ms |
| 30000 units (≈ $0.03 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/2a7cb24c-db61-48a8-8354-d140c6c6931f)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-27 | delisted | {"status":"active"} | {"status":"delisted"} |
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.