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

api.strale.io/x402/v2/deduplicate

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.strale.io/x402/v2/deduplicate
Sourcecdp_bazaar
Declared methodGET
Catalog networkeip155:8453
Receiving address0x66d7c2f952362bfb24fd7f02a9bec9c754ea83bc
Declared price (base units)21600
Catalog statusactive
First seen / last seen2026-09-07 01:03 UTC / 2026-10-06 01:01 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-072026-10-22
Figure 1. Probe timeline, last 14 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-22 16:40 UTCGETpass402182 ms—
2026-10-21 04:40 UTCGETpass4022028 ms—
2026-10-19 16:40 UTCGETpass40264 ms—
2026-10-18 04:40 UTCGETpass402510 ms—
2026-10-16 21:40 UTCGETpass40295 ms—
2026-10-15 12:40 UTCGETpass402147 ms—
2026-10-14 03:40 UTCGETpass402412 ms—
2026-09-30 10:30 UTCGETpass40249 ms—
2026-09-25 10:30 UTCGETpass40289 ms—
2026-09-20 11:24 UTCGETunverified42981 msrate_limitedThe endpoint answered 429; a rate limit is not a verdict on the payment wall.
2026-09-17 12:35 UTCGETpass40223 ms—
2026-09-14 11:24 UTCGETpass40242 ms—
2026-09-10 11:24 UTCGETunverified42924 msrate_limitedThe endpoint answered 429; a rate limit is not a verdict on the payment wall.
2026-09-07 11:24 UTCGETpass40283 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-06relisted{"status":"delisted"}{"status":"active"}
2026-10-03delisted{"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

A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.

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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.

20–2,000 characters · 0 so far

api.strale.io/x402/v2/deduplicate — x402 purchase and probe record | vet402