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

test.x402labs.sh/v1/scraping/scrape

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://test.x402labs.sh/v1/scraping/scrape
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:84532
Receiving address0x3fd04211963f79be7e5356438680542aa97b089f
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-16 01:07 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)14 / 1

2.Probe history

2026-09-012026-09-22
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-22 11:24 UTCPOSTfail400516 msno_402
2026-09-18 11:24 UTCPOSTfail400230 msno_402
2026-09-16 11:24 UTCPOSTfail400492 msno_402
2026-09-12 11:24 UTCPOSTfail400489 msno_402
2026-09-08 11:24 UTCPOSTfail400580 msno_402
2026-09-04 11:24 UTCPOSTfail400593 msno_402
2026-09-01 23:14 UTCPOSTfail400484 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-01relisted{"status":"delisted"}{"status":"active"}
2026-08-31delisted{"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.