Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-19 · 1 day ago

pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/base/token_price/0x0b3e328455c4059eeb9e3f84b5543f74e24e7e1b,0x22af33fe49fd1fa80c7149773dde5890d3c76f3b,0xc0634090f2fe6c6d75e61be2b949464abb498973,0x9b5e262cf9bb04869ab40b19af91d2dc85761722

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/base/token_price/0x0b3e328455c4059eeb9e3f84b5543f74e24e7e1b,0x22af33fe49fd1fa80c7149773dde5890d3c76f3b,0xc0634090f2fe6c6d75e61be2b949464abb498973,0x9b5e262cf9bb04869ab40b19af91d2dc85761722
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-10-20 01:01 UTC
Catalog-reported calls / payers (30d)4 / 4

2.Probe history

2026-08-142026-10-19
Figure 1. Probe timeline, last 10 probes for this endpoint (UTC). Filled = pass, crossed = fail, dashed = unverified. Same-day probes overlap.
L0 probe history, newest first
Probed atMethodVerdictHTTPLatencyReason
2026-10-19 13:40 UTCGETpass402321 ms—
2026-10-01 10:30 UTCGETpass40267 ms—
2026-09-25 10:31 UTCGETpass40285 ms—
2026-09-21 11:24 UTCGETpass40262 ms—
2026-09-17 16:19 UTCGETpass40283 ms—
2026-09-14 11:24 UTCGETpass40260 ms—
2026-09-11 11:24 UTCGETpass40261 ms—
2026-09-07 11:24 UTCGETpass40281 ms—
2026-09-02 11:24 UTCGETpass402126 ms—
2026-08-14 08:53 UTCGETfail40244 msaccepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change).

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. 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-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.

20–2,000 characters · 0 so far