pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/base/token_price/0x0b3e328455c4059eeb9e3f84b5543f74e24e7e1b,0x22af33fe49fd1fa80c7149773dde5890d3c76f3b,0xacfe6019ed1a7dc6f7b508c02d1b04ec88cc21bf
1.Catalog declaration
| Resource URL | https://pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/base/token_price/0x0b3e328455c4059eeb9e3f84b5543f74e24e7e1b,0x22af33fe49fd1fa80c7149773dde5890d3c76f3b,0xacfe6019ed1a7dc6f7b508c02d1b04ec88cc21bf |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x110cdbba7fe6434ec4ce3464cc523942ad6fb784 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 230 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 137 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 323 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 344 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 265 ms | — |
| 2026-10-01 10:30 UTC | GET | pass | 402 | 191 ms | — |
| 2026-09-25 10:31 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 160 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 182 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 68 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 73 ms | accepts_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
1 of 1 paid attempts settled on-chain, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash, and that transaction is the evidence. On this page a receipt means the seller's own settlement receipt (PAYMENT-RESPONSE); a settled row can have none (see “tx from our index”). 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 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 no_declaration- the listing declares no output schema to check the response against.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Latency |
|---|---|---|---|---|
| 10-19 09:312026-10-19 09:31 UTC | settled (nonce-bound) | 200 | 0x3c278ee3…3a0d | 1348 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
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 carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/7eea8934-b4d5-460d-9308-373357bc98ad)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-29 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-27 | delisted | {"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.