Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-21 · today

api.delx.ai/api/v1/x402/token-echo-1

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.delx.ai/api/v1/x402/token-echo-1
Sourcecdp_bazaar
Declared methodPOST
Catalog networkeip155:8453
Receiving address0x9f8bd9875b3e0b632a24a3a7c73f7787175e73a2
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-21 01:01 UTC
Catalog-reported calls / payers (30d)2 / 2

2.Probe history

2026-08-232026-10-21
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-21 10:30 UTCPOSTpass402357 ms—
2026-10-01 10:30 UTCPOSTpass402402 ms—
2026-09-25 10:31 UTCPOSTpass402404 ms—
2026-09-21 11:24 UTCPOSTpass402368 ms—
2026-09-17 16:19 UTCPOSTpass402459 ms—
2026-09-14 11:24 UTCPOSTpass402386 ms—
2026-09-11 11:24 UTCPOSTpass402412 ms—
2026-09-03 11:24 UTCPOSTpass402141 ms—
2026-08-23 10:51 UTCPOSTfail402105 msaccepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's.

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-11relisted{"status":"delisted"}{"status":"active"}
2026-09-07delisted{"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