pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/base/token_price/0x4200000000000000000000000000000000000006,0x940181a94a35a4569e4529a3cdfb74e38fd98631,0x9b5e262cf9bb04869ab40b19af91d2dc85761722
1.Catalog declaration
| Resource URL | https://pro-api.coingecko.com/api/v3/x402/onchain/simple/networks/base/token_price/0x4200000000000000000000000000000000000006,0x940181a94a35a4569e4529a3cdfb74e38fd98631,0x9b5e262cf9bb04869ab40b19af91d2dc85761722 |
| 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) | 6 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-10-01 10:30 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-25 10:31 UTC | GET | pass | 402 | 112 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 155 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 82 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 95 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 58 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 36 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 03:322026-10-19 03:32 UTC | settled (nonce-bound) | 200 | 0x8fda0ac6…1777 | 1071 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/187ea09b-d880-457c-b4a5-a5722b73ef71)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.