Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-09-04 · today

zaref.dev/v1/crypto-prices

1.Catalog declaration

Catalog declaration for this endpoint
Resource URL	https://zaref.dev/v1/crypto-prices
Source	cdp_bazaar
Declared method	GET
Network	eip155:8453
Receiving address	0x6382e6929a20b7eb02bdacfb5368362984b24c15
Declared price (base units)	5000
Catalog status	active
First seen / last seen	2026-08-14 08:52 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)	2 / 2

2.Probe history

2026-08-282026-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 at	Method	Verdict	HTTP	Latency	Reason
2026-09-04 23:40 UTC	GET	pass	402	789 ms	—
2026-09-04 14:40 UTC	GET	pass	402	882 ms	—
2026-09-03 23:40 UTC	GET	pass	402	885 ms	—
2026-09-03 14:40 UTC	GET	pass	402	857 ms	—
2026-09-02 23:40 UTC	GET	pass	402	889 ms	—
2026-09-02 14:40 UTC	GET	pass	402	430 ms	—
2026-08-28 11:01 UTC	GET	fail	402	247 ms	accepts_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 at	Result	HTTP	Receipt (tx)	Latency
09-04 09:242026-09-04 09:24 UTC	settled (amount + payee)	200	0xe0c5f1c5…5617	2898 ms
5000 units (≈ $0.005 USDC) · L2 no_declaration

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 receipt](https://vet402.com/api/badge/endpoint/0c95ad09-ecb0-4994-8ac3-ba74308c89ef.svg)](https://vet402.com/observatory/e/0c95ad09-ecb0-4994-8ac3-ba74308c89ef)

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.