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

blockrun-staging-fee6a95-232500-vbsbhh7lea-uc.a.run.app/api/v1/chat/completions

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://blockrun-staging-fee6a95-232500-vbsbhh7lea-uc.a.run.app/api/v1/chat/completions
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xe9030014f5dae217d0a152f02a043567b16c1abf
Declared price (base units)2000
Catalog statusdelisted (since 2026-09-18 01:03 UTC)
First seen / last seen2026-09-17 01:03 UTC / 2026-09-17 12:35 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-17
Figure 1. Probe timeline, last 3 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-17 22:40 UTCPOSTfail40498 msno_402
2026-09-17 11:24 UTCPOSTfail404329 msno_402
2026-09-17 04:40 UTCPOSTfail404114 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-18delisted{"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.