Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-27 · 6 days ago

agent.memoryapi.org/x402/erc8004/browse

1.Catalog declaration

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

2.Probe history

2026-09-012026-09-27
Figure 1. Probe timeline, last 8 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-27 10:30 UTCGETpass402112 ms—
2026-09-22 11:24 UTCGETpass402108 ms—
2026-09-18 11:24 UTCGETpass40295 ms—
2026-09-16 11:24 UTCGETpass402119 ms—
2026-09-12 11:24 UTCGETpass40286 ms—
2026-09-08 11:24 UTCGETpass40247 ms—
2026-09-03 11:24 UTCGETpass402153 ms—
2026-09-01 11:24 UTCGETfail402199 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

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

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-09-01relisted{"status":"delisted"}{"status":"active"}
2026-08-27delisted{"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.

20–2,000 characters · 0 so far