answerpool.io/v1/sec/insider/clusters
1.Catalog declaration
| Resource URL | https://answerpool.io/v1/sec/insider/clusters |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xb3ba3ca99f9742b32fc527cf62688c83b39aed8c |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-09-03 01:03 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 389 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 412 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 215 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 274 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 182 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 227 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 165 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 127 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 698 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 460 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 542 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 453 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 162 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 3673 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 515 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 2219 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 1138 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 2088 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 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 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-07 01:002026-09-07 01:00 UTC | settled (nonce-bound) | 200 | 0x4c3d9d2b…bc2d | 1482 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 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/a697fc4b-366a-4dfe-be41-c5189d4c3495)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.
About the purchase at 2026-09-07T01:00:34Z (UTC). The form starts with that time; add what you saw instead.