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

api.agentmercantile.com/v1/web-change-snapshot

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.agentmercantile.com/v1/web-change-snapshot
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xdb7b2b54f80479826222749a2ea73a8acc306e1e
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-09-13 01:03 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-132026-09-26
Figure 1. Probe timeline, last 16 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-26 16:40 UTCPOSTfail400235 msno_402
2026-09-25 22:40 UTCPOSTfail400130 msno_402
2026-09-25 04:40 UTCPOSTfail400354 msno_402
2026-09-24 13:40 UTCPOSTfail4002078 msno_402
2026-09-23 16:40 UTCPOSTfail400215 msno_402
2026-09-22 22:40 UTCPOSTfail400200 msno_402
2026-09-22 04:40 UTCPOSTfail400277 msno_402
2026-09-21 13:40 UTCPOSTfail400200 msno_402
2026-09-20 22:40 UTCPOSTfail400397 msno_402
2026-09-20 04:40 UTCPOSTfail400142 msno_402
2026-09-19 13:40 UTCPOSTfail4001821 msno_402
2026-09-18 16:40 UTCPOSTfail400186 msno_402
2026-09-17 22:40 UTCPOSTfail400164 msno_402
2026-09-17 12:35 UTCPOSTfail400302 msno_402
2026-09-14 11:24 UTCPOSTfail400163 msno_402
2026-09-13 11:24 UTCPOSTfail400217 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.