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 |
| Catalog network | eip155:8453 |
| Receiving address | 0x93053f1e7a5efeda532fe69cbbe43cbec3a0f13f |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-11-17 10:05 UTC |
| Catalog-reported calls / payers (30d) | 4 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-11-17 04:40 UTC | POST | pass | 402 | 196 ms | — |
| 2026-11-14 04:40 UTC | POST | pass | 402 | 129 ms | — |
| 2026-11-11 13:40 UTC | POST | pass | 402 | 131 ms | — |
| 2026-11-09 04:40 UTC | POST | pass | 402 | 126 ms | — |
| 2026-11-07 04:40 UTC | POST | pass | 402 | 270 ms | — |
| 2026-11-04 22:40 UTC | POST | pass | 402 | 261 ms | — |
| 2026-11-01 22:40 UTC | POST | pass | 402 | 106 ms | — |
| 2026-10-30 22:40 UTC | POST | pass | 402 | 107 ms | — |
| 2026-10-28 22:40 UTC | POST | pass | 402 | 78 ms | — |
| 2026-10-27 06:40 UTC | POST | pass | 402 | 88 ms | — |
| 2026-10-25 06:40 UTC | POST | pass | 402 | 414 ms | — |
| 2026-10-23 13:40 UTC | POST | pass | 402 | 129 ms | — |
| 2026-10-21 22:40 UTC | POST | pass | 402 | 177 ms | — |
| 2026-10-19 10:30 UTC | POST | pass | 402 | 151 ms | — |
| 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 | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 confirmed on-chain. delivered is a 2xx other than 202 with a non-empty body. A settled row whose paid request answered 5xx counts as settled and not as delivered. definitions.
Terms in this table
settled (nonce-bound)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
settled (amount + payee)- vet402 re-read the transfer on-chain in that chain's pinned settlement asset: the on-chain re-read matched payer, payee, amount and asset and did not bind a one-time value (rows before 2026-09-04, and Stellar).
L2 match- the response parsed as JSON and had each key the declaration marks as required.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
Stage delivered- vet402 re-read the payment on the chain and the paid request returned HTTP 2xx other than 202 Accepted with a body vet402 did not record as empty.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-21 21:312026-10-21 21:31 UTC | settled (nonce-bound) | 200 | 0x377960c9…7086 | BNB Chain | 3064 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered)Stage: delivered | |||||
| 08-28 12:192026-08-28 12:19 UTC | settled (amount + payee) | 200 | 0x47c54af9…b21a | Base | 1685 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered)Stage: delivered | |||||
Add this badge to your docs
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/4c5d2e6e-bd78-499c-b469-27b2559ab02f)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-16 | relisted | {"status":"delisted"} | {"status":"active"} |
| 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. A dispute filed on the record form puts an active listing on a priority list. L0 runs probe that list before their ordinary queue, one run at a time. A listing whose URL has an unfilled path parameter is not put on that list. One run measures up to 50 priority listings, at most 5 from one site. Published fails whose catalog declaration changed, or that rest on probes recorded under earlier rules, take places first, and disputes fill the places left. A listing probed in the past 60 minutes waits for a later run. A dispute that no run reaches within 7 days leaves the list. The scheduled L0 run is at 10:30 UTC, and an L0 run at another time can measure the listing first. The record stays on this page. When a run measures the listing, the new probe is added to its history. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.