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

x402-data-api.sigrunner.workers.dev/crypto/prices

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://x402-data-api.sigrunner.workers.dev/crypto/prices
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x5765ae06a52dc7a0bb71c36a11db512c7ea9ed10
Declared price (base units)1000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-28 01:02 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-242026-09-27
Figure 1. Probe timeline, last 19 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-27 16:40 UTCGETfail402749 msprice_mismatch
2026-09-27 04:40 UTCGETfail402868 msprice_mismatch
2026-09-26 13:40 UTCGETfail402364 msprice_mismatch
2026-09-25 16:40 UTCGETfail4021016 msprice_mismatch
2026-09-24 22:40 UTCGETfail402526 msprice_mismatch
2026-09-24 04:40 UTCGETfail402495 msprice_mismatch
2026-09-23 13:40 UTCGETfail402531 msprice_mismatch
2026-09-22 16:40 UTCGETfail402641 msprice_mismatch
2026-09-21 22:40 UTCGETfail402250 msprice_mismatch
2026-09-21 04:40 UTCGETfail402418 msprice_mismatch
2026-09-20 13:40 UTCGETfail402586 msprice_mismatch
2026-09-19 16:40 UTCGETfail402350 msprice_mismatch
2026-09-18 22:40 UTCGETfail402578 msprice_mismatch
2026-09-18 11:24 UTCGETfail402198 msprice_mismatch
2026-09-15 11:24 UTCGETfail402522 msprice_mismatch
2026-09-11 11:24 UTCGETfail40210 msprice_mismatch
2026-09-08 11:24 UTCGETfail40241 msprice_mismatch
2026-09-03 11:24 UTCGETfail40216 msprice_mismatch
2026-08-24 11:11 UTCGETfail40216 msaccepts_invalid

3.L1 — real purchases

No paid purchases recorded for this endpoint yet.

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

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.