Skip to main content
vet402
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-18 · 1 day ago
vet402Back to the registerMethodology

lin-desk-x402.lindesk.workers.dev/v1/base/token

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://lin-desk-x402.lindesk.workers.dev/v1/base/token
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x4b8ad7ffc8cd960f696059041132339386c28831
Declared price (base units)3000
Catalog statusactive
First seen / last seen2026-10-06 01:09 UTC / 2026-10-18 13:04 UTC
Catalog-reported calls / payers (30d)3 / 3

2.Probe history

2026-10-082026-10-18
Figure 1. Probe timeline, last 10 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-18 22:40 UTCGETpass402326 ms—
2026-10-17 16:40 UTCGETfail502539 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-16 12:40 UTCGETfail502321 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-14 21:40 UTCGETfail502476 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-13 15:40 UTCGETfail502404 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-12 12:40 UTCGETfail502253 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-11 12:40 UTCGETfail502225 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-10 12:40 UTCGETfail50280 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-09 10:31 UTCGETfail50218 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-10-08 13:40 UTCGETfail502256 msno_402HTTP 502 instead of 402 to an unpaid GET.

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