Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-18 · 2 days ago

x402-filings.datalayer.workers.dev/v1/compliance/sanctions-screen

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402-filings.datalayer.workers.dev/v1/compliance/sanctions-screen
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x917e635b83f0dd7e8172c55ec4eebb28b734ca85
Declared price (base units)20000
Catalog statusactive
First seen / last seen2026-08-25 01:58 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)3 / 2

2.Probe history

2026-09-042026-10-18
Figure 1. Probe timeline, last 11 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-10-18 22:40 UTCGETpass402304 ms—
2026-10-17 13:40 UTCGETpass402234 ms—
2026-10-15 21:40 UTCGETpass40246 ms—
2026-10-14 15:40 UTCGETpass402447 ms—
2026-10-13 10:30 UTCGETpass402271 ms—
2026-09-22 11:25 UTCGETpass40217 ms—
2026-09-19 11:24 UTCGETpass402185 ms—
2026-09-16 11:24 UTCGETpass402126 ms—
2026-09-12 11:24 UTCGETpass40221 ms—
2026-09-09 11:24 UTCGETpass40281 ms—
2026-09-04 11:24 UTCGETpass402251 ms—

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