Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-04 · today
vet402Back to the registerMethodology

market.memoryapi.org/x402/market/indices

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://market.memoryapi.org/x402/market/indices
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x24facafeb49b4e3facf0b3e69604a2f4640c9bf2
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-08-18 01:06 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)5 / 1

2.Probe history

2026-09-042026-10-04
Figure 1. Probe timeline, last 9 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-04 10:31 UTCGETpass40266 ms—
2026-09-28 10:30 UTCGETfail2006463 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-23 10:30 UTCGETfail2004076 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-19 11:24 UTCGETfail200529 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-17 11:24 UTCGETfail200422 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-12 11:24 UTCGETfail2001335 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-09 11:24 UTCGETfail200324 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-05 11:24 UTCGETfail200283 msno_402HTTP 200 instead of 402 to an unpaid GET.
2026-09-04 11:24 UTCGETfail200210 msno_402HTTP 200 instead of 402 to an unpaid GET.

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. We first send one confirmation email; nothing else goes out until you confirm.

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.

20–2,000 characters · 0 so far