api.nansen.ai/api/v1/chains/chain-rank
1.Catalog declaration
| Resource URL | https://api.nansen.ai/api/v1/chains/chain-rank |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x93053f1e7a5efeda532fe69cbbe43cbec3a0f13f |
| Declared price (base units) | 10000 |
| Catalog status | delisted (since 2026-09-23 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-22 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-22 13:40 UTC | POST | pass | 402 | 183 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 91 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 190 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 318 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 56 ms | — |
| 2026-09-18 22:40 UTC | POST | pass | 402 | 459 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 145 ms | — |
| 2026-09-17 13:40 UTC | POST | pass | 402 | 134 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 362 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 104 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 102 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 217 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 153 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 82 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 83 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 103 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 218 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 57 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 96 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 76 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 61 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 61 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 312 ms | — |
| 2026-09-07 17:40 UTC | POST | pass | 402 | 70 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 214 ms | — |
| 2026-09-06 17:40 UTC | POST | pass | 402 | 58 ms | — |
| 2026-09-06 05:40 UTC | POST | pass | 402 | 306 ms | — |
| 2026-09-05 17:40 UTC | POST | pass | 402 | 176 ms | — |
| 2026-09-05 05:40 UTC | POST | pass | 402 | 111 ms | — |
| 2026-09-04 17:40 UTC | POST | pass | 402 | 212 ms | — |
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 (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 mismatch- the response lacked 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 |
|---|---|---|---|---|
| 08-28 12:192026-08-28 12:19 UTC | settled (amount + payee) | 200 | 0x47c54af9…b21a | 1685 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose 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/4c5d2e6e-bd78-499c-b469-27b2559ab02f)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-23 | 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.