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

decision-verifier-api.johntaylor1online.workers.dev/verify

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://decision-verifier-api.johntaylor1online.workers.dev/verify
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x463c5fc6bca701970e38d5e8d4cc480a291860db
Declared price (base units)70000
Catalog statusdelisted (since 2026-09-26 01:02 UTC)
First seen / last seen2026-09-10 01:03 UTC / 2026-09-25 01:02 UTC
Catalog-reported calls / payers (30d)9 / 1

2.Probe history

2026-09-102026-09-25
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-25 10:30 UTCPOSTfail404120 msno_402
2026-09-21 11:24 UTCPOSTfail402241 msprice_mismatch
2026-09-17 12:35 UTCPOSTfail402334 msprice_mismatch
2026-09-14 11:24 UTCPOSTfail402124 msprice_mismatch
2026-09-11 11:24 UTCPOSTfail402212 msprice_mismatch
2026-09-10 11:24 UTCPOSTfail402135 msprice_mismatch

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-26delisted{"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.