blockrun.ai/api/v1/defillama/prices/coingecko:ronin,coingecko:axie-infinity
1.Catalog declaration
| Resource URL | https://blockrun.ai/api/v1/defillama/prices/coingecko:ronin,coingecko:axie-infinity |
| 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-17 01:06 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 6 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-03 16:40 UTC | GET | pass | 402 | 510 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 53 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 215 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 2130 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 330 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 261 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 240 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 232 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 591 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 51 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 246 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 165 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-01 23:14 UTC | GET | pass | 402 | 106 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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 |
|---|---|---|---|---|
| 09-30 12:022026-09-30 12:02 UTC | settled (nonce-bound) | 200 | 0x8269cb12…e0d9 | 1965 ms |
| 2000 units (≈ $0.002 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-18 12:082026-09-18 12:08 UTC | settled (nonce-bound) | 200 | 0x51dc081e…728a | 1336 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 2/2 settled · 2 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/9ae96838-37a2-41b5-834f-ed9a276a6a7a)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.