x402.coinopai.com/api/kronos/forecast
1.Catalog declaration
| Resource URL | https://x402.coinopai.com/api/kronos/forecast |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x1304ec1a8945365e43a5c18a734065f107b417ca |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 22:40 UTC | GET | pass | 402 | 316 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 2092 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 52 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 516 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 83 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 282 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 246 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 212 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 188 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 232 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 259 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 100 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 252 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 363 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 2200 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 584 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 71 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 2269 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 402 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 2118 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 381 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-02 11:25 UTC | GET | pass | 402 | 35 ms | — |
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 |
|---|---|---|---|---|
| 10-01 15:322026-10-01 15:32 UTC | settled (nonce-bound) | 200 | 0x690f3d1f…4a1b | 1354 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-11 06:012026-09-11 06:01 UTC | settled (nonce-bound) | 200 | 0xc6e5e7b4…11e8 | 1416 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/4036d7b7-3cec-44b9-9131-023128887d47)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-26 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-23 | 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.