Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · today
lionx402.com/api/x402/vat-validation-json
1.Catalog declaration
| Resource URL | https://lionx402.com/api/x402/vat-validation-json |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x68e3e7822cf83c824cf9606ec999b5e8a93c85b5 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
2026-08-162026-10-20
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 13:40 UTC | GET | pass | 402 | 833 ms | — |
| 2026-10-02 10:30 UTC | GET | pass | 402 | 369 ms | — |
| 2026-09-26 10:30 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-15 11:24 UTC | GET | fail | — | 10000 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-11 11:24 UTC | GET | fail | — | 10000 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 1159 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 1073 ms | — |
| 2026-08-16 10:39 UTC | GET | fail | 402 | 383 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
No paid purchases recorded for this endpoint yet.
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-28 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-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.