api.deepnets.ai/api/flagged-tokens
1.Catalog declaration
| Resource URL | https://api.deepnets.ai/api/flagged-tokens |
| 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) | 3 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 301 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 440 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 246 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 2278 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 213 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 253 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 12 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-27 18:002026-09-27 18:00 UTC | settled (nonce-bound) | 200 | 3qrvQkS1Xw…4WAP | 1319 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-21 12:082026-09-21 12:08 UTC | settled (nonce-bound) | 200 | 3vfPAkHS4k…h6Uj | 2231 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/fad1b9cb-970f-4e45-9e41-db0f5c6c2519)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-16 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-03 | 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.