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

api.memestack.ai/v1/agent/reverse-search

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.memestack.ai/v1/agent/reverse-search
Sourcecdp_bazaar
Declared methodPOST
Networkeip155:8453
Receiving address0xa06c42daa258595bc773a0bf032a5ba55939781a
Declared price (base units)17000
Catalog statusdelisted (since 2026-09-21 01:03 UTC)
First seen / last seen2026-09-07 01:03 UTC / 2026-09-20 01:03 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-09-072026-09-20
Figure 1. Probe timeline, last 10 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-20 22:40 UTCPOSTfail400183 msno_402
2026-09-20 04:40 UTCPOSTfail400224 msno_402
2026-09-19 13:40 UTCPOSTfail400336 msno_402
2026-09-18 16:40 UTCPOSTfail400215 msno_402
2026-09-17 22:40 UTCPOSTfail400311 msno_402
2026-09-17 13:40 UTCPOSTfail400627 msno_402
2026-09-15 11:24 UTCPOSTfail400146 msno_402
2026-09-11 11:24 UTCPOSTfail40058 msno_402
2026-09-08 11:24 UTCPOSTfail400160 msno_402
2026-09-07 11:24 UTCPOSTfail40022 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-21delisted{"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.

api.memestack.ai/v1/agent/reverse-search — L0 observations | vet402