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

api.dexl.io/api/tokens

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://api.dexl.io/api/tokens
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x0ccd097f92475d3eaf88e3b73e38a4dd4cb08667
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-08-30 01:02 UTC / 2026-09-29 01:03 UTC
Catalog-reported calls / payers (30d)14 / 1

2.Probe history

2026-09-082026-09-28
Figure 1. Probe timeline, last 30 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-09-28 16:40 UTCGETpass402587 ms—
2026-09-28 04:40 UTCGETpass402697 ms—
2026-09-26 13:40 UTCGETfail502517 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-09-25 22:40 UTCGETfail502998 msno_402HTTP 502 instead of 402 to an unpaid GET.
2026-09-25 04:40 UTCGETpass402861 ms—
2026-09-24 13:40 UTCGETpass402723 ms—
2026-09-23 16:40 UTCGETpass402564 ms—
2026-09-22 22:40 UTCGETpass402741 ms—
2026-09-22 04:40 UTCGETpass402569 ms—
2026-09-21 13:40 UTCGETpass402482 ms—
2026-09-20 16:40 UTCGETpass402597 ms—
2026-09-19 22:40 UTCGETpass402513 ms—
2026-09-19 04:40 UTCGETpass402535 ms—
2026-09-18 13:40 UTCGETpass402688 ms—
2026-09-17 16:40 UTCGETpass4021193 ms—
2026-09-17 04:40 UTCGETpass402493 ms—
2026-09-16 13:40 UTCGETpass402458 ms—
2026-09-15 16:40 UTCGETpass402616 ms—
2026-09-14 22:40 UTCGETpass402535 ms—
2026-09-14 04:40 UTCGETpass4022439 ms—
2026-09-13 16:40 UTCGETpass402448 ms—
2026-09-13 04:40 UTCGETpass402727 ms—
2026-09-12 13:40 UTCGETpass402462 ms—
2026-09-11 22:40 UTCGETfail402636 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-11 04:40 UTCGETfail402548 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-10 17:40 UTCGETfail402468 msmetadata_mismatchpayTo or network differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-10 05:40 UTCGETpass402473 ms—
2026-09-09 14:40 UTCGETpass402533 ms—
2026-09-08 23:40 UTCGETpass4022371 ms—
2026-09-08 14:40 UTCGETpass402976 ms—

3.L1 — real purchases

1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.

Terms in this table

settled (nonce-bound)
vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 mismatch
the response lacked fields the listing's output schema declares.
Whose side
the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
1/1
Figure 2. Settle-through: one cell per paid attempt. Filled = settled with an on-chain receipt, crossed = paid but no receipt.
L1 purchase history, newest first
Attempted atResultHTTPReceipt (tx)Latency
09-05 12:07settled (nonce-bound)2000x687d59af…ef3e2339 ms
1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.

vet402: 1 of 1 paid attempts settled with an on-chain receipt, and 1 of those also returned a 2xx response. settled is the confirmed transfer; delivered is the response arriving. A measurement of what happened when vet402 paid this endpoint, not a recommendation. (api.dexl.io · measured 2026-09-05)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/64a01fe1-33de-4340-b96e-7e67a6f0d0ef.svg)](https://vet402.com/observatory/e/64a01fe1-33de-4340-b96e-7e67a6f0d0ef)

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-28relisted{"status":"delisted"}{"status":"active"}
2026-09-27delisted{"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.

About the purchase at 2026-09-05T12:07:48Z (UTC). The form starts with that time; add what you saw instead.

20–2,000 characters · 59 so far