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

api.munition.io/v1/exa/answer

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.munition.io/v1/exa/answer
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0x54d6c2c08e10f1a1d3da88df513bbe9bcf1a4afa
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-09-10 01:03 UTC / 2026-09-27 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-102026-09-27
Figure 1. Probe timeline, last 25 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-27 04:40 UTCPOSTfail400181 msno_402
2026-09-26 13:40 UTCPOSTfail400149 msno_402
2026-09-25 16:40 UTCPOSTfail400667 msno_402
2026-09-24 22:40 UTCPOSTfail40096 msno_402
2026-09-24 13:40 UTCPOSTfail400960 msno_402
2026-09-23 16:40 UTCPOSTfail400572 msno_402
2026-09-22 22:40 UTCPOSTfail400121 msno_402
2026-09-22 04:40 UTCPOSTfail400213 msno_402
2026-09-21 13:40 UTCPOSTfail400121 msno_402
2026-09-20 16:40 UTCPOSTfail400101 msno_402
2026-09-19 22:40 UTCPOSTfail400133 msno_402
2026-09-19 04:40 UTCPOSTfail400100 msno_402
2026-09-18 13:40 UTCPOSTfail400195 msno_402
2026-09-17 22:40 UTCPOSTfail400123 msno_402
2026-09-17 04:40 UTCPOSTfail400139 msno_402
2026-09-16 13:40 UTCPOSTfail400315 msno_402
2026-09-15 16:40 UTCPOSTfail400191 msno_402
2026-09-14 22:40 UTCPOSTfail400106 msno_402
2026-09-14 13:40 UTCPOSTfail400106 msno_402
2026-09-13 16:40 UTCPOSTfail400217 msno_402
2026-09-13 04:40 UTCPOSTfail400183 msno_402
2026-09-12 13:40 UTCPOSTfail400299 msno_402
2026-09-11 22:40 UTCPOSTfail4003136 msno_402
2026-09-11 11:24 UTCPOSTfail400319 msno_402
2026-09-10 11:24 UTCPOSTfail40042 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.