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

vending-machine-seven.vercel.app/api/v/crypto-prices

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://vending-machine-seven.vercel.app/api/v/crypto-prices
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0xc648116b5debe4af7d78838aa468d07e0a9ab697
Declared price (base units)5000
Catalog statusactive
First seen / last seen2026-08-14 08:52 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)6 / 2

2.Probe history

2026-08-302026-09-04
Figure 1. Probe timeline, last 7 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-04 17:40 UTCGETpass402151 ms—
2026-09-04 05:40 UTCGETpass402292 ms—
2026-09-03 23:40 UTCGETpass40255 ms—
2026-09-03 14:40 UTCGETpass402290 ms—
2026-09-02 23:40 UTCGETpass40256 ms—
2026-09-02 14:40 UTCGETpass40286 ms—
2026-08-30 11:24 UTCGETfail40263 msaccepts_invalid

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 4xx or 5xx counts as settled and not as delivered — definitions.

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-03 19:01settled (amount + payee)2000x6570e60c…5a7d1170 ms
5000 units (≈ $0.005 USDC) · L2 match

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 states a measurement, not a rating.

vet402: 1 of 1 paid attempts settled, 1 delivered

[![vet402 receipt](https://vet402.com/api/badge/endpoint/b501a0e3-b780-41bb-aa55-41291dd6c594.svg)](https://vet402.com/observatory/e/b501a0e3-b780-41bb-aa55-41291dd6c594)

Get one email when this record's verdict changes. No digest, no marketing — one message per change, and only for this endpoint.

4.Catalog listing events

Catalog listing events, newest first
Detected onEventBeforeAfter
2026-08-25relisted{"status":"delisted"}{"status":"active"}
2026-08-24delisted{"status":"active"}{"status":"delisted"}
2026-08-20relisted{"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.