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

402agent.ai/agent402/api/v1/read

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://402agent.ai/agent402/api/v1/read
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x6d0ab33a11f03fe782eaa949dea7785bae16ebc7
Declared price (base units)47000
Catalog statusactive
First seen / last seen2026-09-17 12:35 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-172026-09-25
Figure 1. Probe timeline, last 4 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap. Marks closer than one mark width are stepped down one lane.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-25 10:30 UTCPOSTfail400227 msno_402
2026-09-21 11:24 UTCPOSTfail400157 msno_402
2026-09-17 16:19 UTCPOSTfail400340 msno_402
2026-09-17 12:35 UTCPOSTfail400399 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

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.