stockwaves.net/api/anomalies/insight
1.Catalog declaration
| Resource URL | https://stockwaves.net/api/anomalies/insight |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xdc9f94a8b93f070b58cfa580cbe740d763005fe6 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 13:40 UTC | GET | pass | 402 | 295 ms | — |
| 2026-10-18 16:40 UTC | GET | pass | 402 | 784 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 563 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 4256 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 696 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 6915 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 279 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 760 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 610 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 985 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 263 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 1331 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 292 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 1101 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 847 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 972 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 639 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 2663 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 843 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 831 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 771 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 898 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 836 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 852 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 909 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 807 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 753 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 762 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 734 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 692 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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 |
|---|---|---|---|---|
| 10-07 09:302026-10-07 09:30 UTC | settled (nonce-bound) | 200 | 0x67212167…b91e | 2162 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 10-01 06:002026-10-01 06:00 UTC | settled (nonce-bound) | 200 | 0x8e7af0d5…cf4d | 2357 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-08 12:092026-09-08 12:09 UTC | settled (nonce-bound) | 200 | 0x9786d7bf…3651 | 1808 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/77b65b29-14aa-46d8-b894-d28858bf98fb)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-06 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-06 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-09-07 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-06 | 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.