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

bykaranteli.com/api/x402/liqmap-levels

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://bykaranteli.com/api/x402/liqmap-levels
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xb4c6c903dee310e4060d8e6eb68582426be1baa9
Declared price (base units)100000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)10 / 3

2.Probe history

2026-09-222026-10-19
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-10-19 13:40 UTCGETpass402131 ms—
2026-10-17 22:40 UTCGETpass402256 ms—
2026-10-16 15:40 UTCGETpass402206 ms—
2026-10-15 03:40 UTCGETpass402233 ms—
2026-10-13 21:40 UTCGETpass402298 ms—
2026-10-12 15:40 UTCGETpass402279 ms—
2026-10-11 12:40 UTCGETpass4022003 ms—
2026-10-10 12:40 UTCGETpass4021931 ms—
2026-10-09 12:40 UTCGETpass402168 ms—
2026-10-08 04:40 UTCGETpass402110 ms—
2026-10-07 04:40 UTCGETpass402133 ms—
2026-10-06 04:41 UTCGETpass402159 ms—
2026-10-04 22:40 UTCGETpass402160 ms—
2026-10-04 04:40 UTCGETpass402155 ms—
2026-10-03 04:40 UTCGETpass402306 ms—
2026-10-02 13:40 UTCGETfail402143 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-10-01 16:40 UTCGETfail402189 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-30 22:40 UTCGETfail402122 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-30 04:40 UTCGETfail402530 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-29 10:30 UTCGETfail402301 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-29 07:38 UTCGETfail402261 msprice_mismatchDeclared 5000 of 0x8335…2913; the 402 offered 100000 of 0x8335…2913, 100000 of EPjFWd…Dt1v.
2026-09-28 16:40 UTCGETfail402299 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 22:40 UTCGETfail402325 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-27 04:40 UTCGETfail402347 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-26 13:40 UTCGETfail402271 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-25 16:40 UTCGETfail402216 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 22:40 UTCGETfail402210 msprice_mismatchAmount or asset differs from the catalog declaration (the values compared were not recorded before the 2026-09-29 change).
2026-09-24 04:40 UTCGETpass402420 ms—
2026-09-23 13:40 UTCGETpass4022295 ms—
2026-09-22 16:40 UTCGETpass402216 ms—

3.L1 — real purchases

1 of 1 paid attempts settled on-chain, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). 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 on-chain, crossed = signed, and not settled on-chain.
L1 purchase history, newest first
Attempted atResultHTTPOn-chain txLatency
09-21 18:00settled (nonce-bound)2003r6eb2P78g…2HDh4671 ms
5000 units (≈ $0.005 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. (bykaranteli.com · measured 2026-09-21)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/6d3dc235-90cb-416a-8656-14089e98a7ce.svg)](https://vet402.com/observatory/e/6d3dc235-90cb-416a-8656-14089e98a7ce)

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-03relisted{"status":"delisted"}{"status":"active"}
2026-08-18delisted{"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