Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: failLast probed: 2026-09-25 · 1 day ago
vet402Back to the registerMethodology

minia2a.uk/x402/payment-audit

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://minia2a.uk/x402/payment-audit
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xab62452b4b019bc4402bffcca6c706d16d72a7bf
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-09-04 01:03 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)4 / 1

2.Probe history

2026-09-052026-09-25
Figure 1. Probe timeline, last 7 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-25 10:30 UTCPOSTfail402140 msprice_mismatch
2026-09-20 11:24 UTCPOSTfail402312 msprice_mismatch
2026-09-17 12:35 UTCPOSTfail402192 msprice_mismatch
2026-09-14 11:24 UTCPOSTfail402206 msprice_mismatch
2026-09-10 11:24 UTCPOSTunverified429126 msrate_limited
2026-09-07 11:24 UTCPOSTfail402304 msprice_mismatch
2026-09-05 11:24 UTCPOSTfail40359 msno_402

3.L1 — real purchases

No paid 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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-07relisted{"status":"delisted"}{"status":"active"}
2026-09-06delisted{"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.