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

pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/base/token_price/0x4200000000000000000000000000000000000006,0x940181a94a35a4569e4529a3cdfb74e38fd98631,0x9b5e262cf9bb04869ab40b19af91d2dc85761722,0xacfe6019ed1a7dc6f7b508c02d1b04ec88cc21bf,0x22af33fe49fd1fa80c7149773dde5890d3c76f3b

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/base/token_price/0x4200000000000000000000000000000000000006,0x940181a94a35a4569e4529a3cdfb74e38fd98631,0x9b5e262cf9bb04869ab40b19af91d2dc85761722,0xacfe6019ed1a7dc6f7b508c02d1b04ec88cc21bf,0x22af33fe49fd1fa80c7149773dde5890d3c76f3b
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x110cdbba7fe6434ec4ce3464cc523942ad6fb784
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-14 08:39 UTC / 2026-09-05 01:03 UTC
Catalog-reported calls / payers (30d)1 / 1

2.Probe history

2026-08-142026-09-02
Figure 1. Probe timeline, last 2 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-09-02 11:24 UTCGETpass402148 ms—
2026-08-14 08:53 UTCGETfail40246 msaccepts_invalid

3.L1 — real purchases

No covert 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

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