agent.massive.com/stocks/filings/8-K/vX/text
1.Catalog declaration
| Resource URL | https://agent.massive.com/stocks/filings/8-K/vX/text |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x525f6ddce9af7a7179d7696aabfcd5fcd15a21e6 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-31 01:03 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 13 / 9 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 16:40 UTC | GET | pass | 402 | 131 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 42 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 54 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 40 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 14 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 71 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 28 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 17 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 157 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 47 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 40 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 34 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 15 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 605 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 792 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 24 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 18 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 1744 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 169 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 38 ms | — |
| 2026-09-04 11:24 UTC | GET | pass | 402 | 7 ms | — |
3.L1 — real purchases
3 of 3 paid attempts settled with a receipt, and 3 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 mismatch- the response lacked 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-23 12:012026-09-23 12:01 UTC | settled (nonce-bound) | 200 | 0x30a0294c…4282 | 1374 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-17 00:022026-09-17 00:02 UTC | settled (nonce-bound) | 200 | 0xc8bfb673…4f5d | 1366 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-10 19:002026-09-10 19:00 UTC | settled (nonce-bound) | 200 | 0x21cba633…b802 | 1861 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose 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/75e87b05-6da0-4217-9466-d8a575d58665)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-10T19:00:03Z (UTC). The form starts with that time; add what you saw instead.