blockrun.ai/api/v1/defillama/prices/coingecko:bitcoin,coingecko:ethereum,coingecko:solana
1.Catalog declaration
| Resource URL | https://blockrun.ai/api/v1/defillama/prices/coingecko:bitcoin,coingecko:ethereum,coingecko:solana |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xe9030014f5dae217d0a152f02a043567b16c1abf |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 9 / 6 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | GET | pass | 402 | 181 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 2401 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 95 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 1795 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-10-05 22:40 UTC | GET | pass | 402 | 2110 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 74 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 237 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 397 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 301 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 440 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 117 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 286 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 64 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 match- the response had the fields the listing's output schema declares.
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-08 21:312026-10-08 21:31 UTC | settled (nonce-bound) | 200 | 0x01d61fae…6d86 | 1999 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-29 21:322026-09-29 21:32 UTC | settled (nonce-bound) | 200 | 0xcd3213fd…31e5 | 2417 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-18 06:012026-09-18 06:01 UTC | settled (nonce-bound) | 200 | 0x17777ef0…9cdf | 1546 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/578e925b-a576-48bf-9958-6d2184c935aa)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.