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

manyfish-seller.redcliff-d7368db1.westus2.azurecontainerapps.io/api/v1/image/caption

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://manyfish-seller.redcliff-d7368db1.westus2.azurecontainerapps.io/api/v1/image/caption
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x9cd3f0d8a73a9a87f752f09d220652dc7de398cc
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-09-02 01:03 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)2 / 1

2.Probe history

2026-09-022026-09-04
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-04 23:40 UTCPOSTpass402317 ms—
2026-09-04 14:40 UTCPOSTpass402222 ms—
2026-09-03 23:40 UTCPOSTpass402229 ms—
2026-09-03 14:40 UTCPOSTpass4022037 ms—
2026-09-03 05:40 UTCPOSTpass402259 ms—
2026-09-02 17:40 UTCPOSTpass402301 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.