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

vmi1759441.contaboserver.net/api/x402/ugc-product-video

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://vmi1759441.contaboserver.net/api/x402/ugc-product-video
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x3795cd5eaa98dbfad6b7445132302af0b4b92a39
Declared price (base units)600000
Catalog statusdelisted (since 2026-09-22 01:03 UTC)
First seen / last seen2026-08-14 08:39 UTC / 2026-09-21 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-242026-09-18
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-18 11:24 UTCPOSTfail402631 msprice_mismatch
2026-09-15 11:24 UTCPOSTfail402253 msprice_mismatch
2026-09-11 11:24 UTCPOSTfail402126 msprice_mismatch
2026-09-08 11:24 UTCPOSTfail402354 msprice_mismatch
2026-09-03 11:24 UTCPOSTfail402218 msprice_mismatch
2026-08-24 11:11 UTCPOSTfail402126 msaccepts_invalid

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-22delisted{"status":"active"}{"status":"delisted"}
2026-08-21relisted{"status":"delisted"}{"status":"active"}
2026-08-19delisted{"status":"active"}{"status":"delisted"}
2026-08-17relisted{"status":"delisted"}{"status":"active"}
2026-08-16delisted{"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.