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

www.x402scan.com/api/x402/merchants/:address/transactions

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://www.x402scan.com/api/x402/merchants/:address/transactions
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x2ec4545f96a24876764bf2b04d54e66a1351be71
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC
Catalog-reported calls / payers (30d)87 / 6

2.Probe history

2026-08-242026-09-02
Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-02 05:40 UTCGETpass402129 ms—
2026-08-24 11:11 UTCGETfail402474 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

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