Skip to main content
Independent MeasurementEndpoint record (L0 · L1)Published state: passLast probed: 2026-10-20 · today

pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/monad/token_price/probe

1.Catalog declaration

Catalog declaration for this endpoint
Resource URLhttps://pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/monad/token_price/probe
Sourcecdp_bazaar
Declared methodGET
Networkeip155:8453
Receiving address0x110cdbba7fe6434ec4ce3464cc523942ad6fb784
Declared price (base units)10000
Catalog statusactive
First seen / last seen2026-08-29 01:11 UTC / 2026-10-20 01:01 UTC
Catalog-reported calls / payers (30d)4 / 4

2.Probe history

2026-09-042026-10-20
Figure 1. Probe timeline, last 24 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-10-20 04:40 UTCGETpass40281 ms—
2026-10-18 16:40 UTCGETpass402812 ms—
2026-10-17 04:40 UTCGETpass40281 ms—
2026-10-15 15:40 UTCGETpass402151 ms—
2026-10-14 12:40 UTCGETpass402146 ms—
2026-10-13 03:40 UTCGETpass40270 ms—
2026-10-12 03:40 UTCGETpass402184 ms—
2026-10-10 21:40 UTCGETpass402228 ms—
2026-10-09 21:40 UTCGETpass4022088 ms—
2026-10-08 16:40 UTCGETpass40298 ms—
2026-10-07 16:40 UTCGETpass4021791 ms—
2026-10-06 16:40 UTCGETpass402127 ms—
2026-10-05 22:40 UTCGETpass40280 ms—
2026-10-04 13:40 UTCGETpass402376 ms—
2026-10-03 16:40 UTCGETpass402149 ms—
2026-10-02 22:40 UTCGETpass402386 ms—
2026-10-02 04:40 UTCGETpass402362 ms—
2026-09-27 10:30 UTCGETpass402144 ms—
2026-09-22 11:25 UTCGETpass40263 ms—
2026-09-19 11:24 UTCGETpass40261 ms—
2026-09-16 11:24 UTCGETpass40258 ms—
2026-09-12 11:24 UTCGETpass40269 ms—
2026-09-09 11:24 UTCGETpass40261 ms—
2026-09-04 11:24 UTCGETpass40262 ms—

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

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.

20–2,000 characters · 0 so far