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

organiccryptoyyc.com:8443/v1/pokt/supplier-trust/:operatorId

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://organiccryptoyyc.com:8443/v1/pokt/supplier-trust/:operatorId
Sourcecdp_bazaar
Declared methodGET
Networksolana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
Receiving addressHYhhZ1gH4bKLGFnbnE3RukQ1s1G7fz9cTcuHiV1Zymje
Declared price (base units)50000
Catalog statusactive
First seen / last seen2026-08-16 01:07 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-01
Figure 1. Probe timeline, last 1 probe for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-01 23:14 UTCGETpass4021168 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.