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

finance-api.kdlcfa.workers.dev/cpi-us

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://finance-api.kdlcfa.workers.dev/cpi-us
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xe3738580ede5384bb8b8d1c8786b391c59d2668d
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-24 02:00 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-09-042026-10-20
Figure 1. Probe timeline, last 21 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-20 10:30 UTCGETpass402794 ms—
2026-09-17 04:40 UTCGETfail50392 msno_402HTTP 503 instead of 402 to an unpaid GET.
2026-09-16 16:40 UTCGETpass402771 ms—
2026-09-15 16:40 UTCGETpass402347 ms—
2026-09-15 04:40 UTCGETpass402739 ms—
2026-09-12 13:40 UTCGETpass402836 ms—
2026-09-11 22:40 UTCGETpass4022530 ms—
2026-09-11 13:40 UTCGETfail503110 msno_402HTTP 503 instead of 402 to an unpaid GET.
2026-09-10 17:40 UTCGETpass402454 ms—
2026-09-10 05:40 UTCGETpass402607 ms—
2026-09-09 17:40 UTCGETpass402744 ms—
2026-09-08 23:40 UTCGETpass402627 ms—
2026-09-08 14:40 UTCGETpass4021075 ms—
2026-09-07 23:40 UTCGETpass402490 ms—
2026-09-07 14:40 UTCGETpass402361 ms—
2026-09-06 23:40 UTCGETpass402365 ms—
2026-09-06 14:40 UTCGETpass402547 ms—
2026-09-05 23:40 UTCGETpass402469 ms—
2026-09-05 14:40 UTCGETpass402514 ms—
2026-09-04 17:40 UTCGETpass402842 ms—
2026-09-04 11:24 UTCGETpass402297 ms—

3.L1 — real purchases

2 of 2 paid attempts settled on-chain, and 2 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 no_declaration
the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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).
2/2
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-15 23:50settled (nonce-bound)2000x8be977e6…a5e71981 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)
09-04 12:08settled (nonce-bound)2000x58a7c56f…93112041 ms
10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered)

Embed this record

Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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: 2 of 2 paid attempts settled with an on-chain receipt, and 2 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. (finance-api.kdlcfa.workers.dev · measured 2026-09-15)

[![vet402 receipt](https://vet402.com/api/badge/endpoint/9d70452a-978b-4ef9-8cd6-e962d0d2aa70.svg)](https://vet402.com/observatory/e/9d70452a-978b-4ef9-8cd6-e962d0d2aa70)

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-20relisted{"status":"delisted"}{"status":"active"}
2026-09-17delisted{"status":"active"}{"status":"delisted"}
2026-09-15relisted{"status":"delisted"}{"status":"active"}
2026-09-13delisted{"status":"active"}{"status":"delisted"}
2026-08-30relisted{"status":"delisted"}{"status":"active"}
2026-08-26delisted{"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

finance-api.kdlcfa.workers.dev/cpi-us — x402 purchase and probe record | vet402