vending-machine-seven.vercel.app/api/v/kronos-forecast
1.Catalog declaration
| Resource URL | https://vending-machine-seven.vercel.app/api/v/kronos-forecast |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc648116b5debe4af7d78838aa468d07e0a9ab697 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 16:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 250 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 508 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 262 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 211 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 1867 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 324 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 2017 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 1929 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 85 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 307 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 100 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 46 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-09 11:24 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 33 ms | — |
| 2026-08-28 11:01 UTC | GET | fail | 402 | 1072 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 0 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.
A row marked tx from our index came back with no settlement receipt from the seller. Our own index of on-chain settlements found the transfer afterwards — our payer, this endpoint's payee, the exact amount, inside the time window — and the row goes through the same on-chain re-read as any other before it reads settled. The seller did not name that transaction; we did (methodology).
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 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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-17 00:002026-09-17 00:00 UTC | settled (nonce-bound)tx from our index | — | 0x386e6a2e…60fe | 20141 ms |
| 50000 units (≈ $0.05 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 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/e00370b6-83b1-4bc4-b625-4ac874bf61a2)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-09 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-08 | 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.