Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-04 · today
vet402Back to the registerMethodology

lionx402.com/api/x402/tx-receipt-decoded-json

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://lionx402.com/api/x402/tx-receipt-decoded-json
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x68e3e7822cf83c824cf9606ec999b5e8a93c85b5
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-28 01:11 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-022026-09-04
Figure 1. Probe timeline, last 6 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-04 17:40 UTCGETpass402812 ms—
2026-09-04 05:40 UTCGETpass402675 ms—
2026-09-03 23:40 UTCGETpass4021188 ms—
2026-09-03 14:40 UTCGETpass4021171 ms—
2026-09-02 23:40 UTCGETpass402180 ms—
2026-09-02 14:40 UTCGETpass402617 ms—

3.L1 — real purchases

No covert purchases recorded for this endpoint yet.

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

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.