api.nansen.ai/api/v1/tgm/holders
1.Catalog declaration
| Resource URL | https://api.nansen.ai/api/v1/tgm/holders |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x93053f1e7a5efeda532fe69cbbe43cbec3a0f13f |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 130 / 12 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | POST | pass | 402 | 364 ms | — |
| 2026-09-28 13:40 UTC | POST | pass | 402 | 676 ms | — |
| 2026-09-27 16:40 UTC | POST | pass | 402 | 92 ms | — |
| 2026-09-26 22:40 UTC | POST | pass | 402 | 107 ms | — |
| 2026-09-26 13:40 UTC | POST | pass | 402 | 137 ms | — |
| 2026-09-25 16:40 UTC | POST | pass | 402 | 475 ms | — |
| 2026-09-24 22:40 UTC | POST | pass | 402 | 235 ms | — |
| 2026-09-24 04:40 UTC | POST | pass | 402 | 571 ms | — |
| 2026-09-23 13:40 UTC | POST | pass | 402 | 124 ms | — |
| 2026-09-22 16:40 UTC | POST | pass | 402 | 1873 ms | — |
| 2026-09-21 22:40 UTC | POST | pass | 402 | 126 ms | — |
| 2026-09-21 04:40 UTC | POST | pass | 402 | 92 ms | — |
| 2026-09-20 13:40 UTC | POST | pass | 402 | 85 ms | — |
| 2026-09-19 16:40 UTC | POST | pass | 402 | 57 ms | — |
| 2026-09-19 04:40 UTC | POST | pass | 402 | 478 ms | — |
| 2026-09-17 16:19 UTC | POST | pass | 402 | 259 ms | — |
| 2026-09-14 11:24 UTC | POST | pass | 402 | 57 ms | — |
| 2026-09-11 11:24 UTC | POST | pass | 402 | 56 ms | — |
| 2026-09-07 11:24 UTC | POST | pass | 402 | 95 ms | — |
| 2026-09-02 11:24 UTC | POST | pass | 402 | 91 ms | — |
| 2026-08-14 08:53 UTC | POST | fail | 402 | 66 ms | accepts_invalidRecorded before the 2026-09-29 change, when the probe read only the first 4,000 bytes of the 402 body; this body began like an x402 envelope, so the fail may be vet402's measuring error rather than the seller's. |
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-25 12:022026-09-25 12:02 UTC | settled (nonce-bound) | 200 | 0x5d75c774…17ff | 2325 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-19 06:012026-09-19 06:01 UTC | settled (nonce-bound) | 200 | 0xbb82f08d…4e10 | 1667 ms |
| 50000 units (≈ $0.05 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/85e458f2-e4b5-4e24-9783-e2a8d0ba8178)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.