api.deepnets.ai/api/watchlist
1.Catalog declaration
| Resource URL | https://api.deepnets.ai/api/watchlist |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | Bn7sLNmcL9ru5kt9gNwVn8e8Sx912dBTxiUBNiwjbiY8 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 154 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 386 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 223 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 229 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 149 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 108 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 2101 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 192 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 563 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 94 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 159 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 266 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 445 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 160 ms | — |
| 2026-08-14 08:52 UTC | GET | fail | 402 | 60 ms | accepts_invalid |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 2 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-26 06:002026-09-26 06:00 UTC | settled (nonce-bound) | 200 | 4bXVvbYJaE…xs3E | 1352 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-20 00:002026-09-20 00:00 UTC | settled (nonce-bound) | 200 | 5oR9Gjx3y9…ZWg1 | 1187 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 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/0fd03001-cf3e-4708-b696-668c9e96646a)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.