kronossignals.com/api/v1/scan
1.Catalog declaration
| Resource URL | https://kronossignals.com/api/v1/scan |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x36038e1d712c5e39f35952164ec58ec2b96caee7 |
| Declared price (base units) | 40000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 10:31 UTC | GET | pass | 402 | 189 ms | — |
| 2026-09-26 10:30 UTC | GET | pass | 402 | 125 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 126 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 440 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 127 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 2086 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 403 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 81 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 181 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 277 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 278 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 1002 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 60 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 60 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 51 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-09-06 14:40 UTC | GET | pass | 402 | 46 ms | — |
| 2026-09-05 23:40 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-05 14:40 UTC | GET | pass | 402 | 1072 ms | — |
| 2026-09-04 23:40 UTC | GET | pass | 402 | 707 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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 (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
L2 no_declaration- the listing declares no output schema to check the response against.
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 |
|---|---|---|---|---|
| 08-14 10:092026-08-14 10:09 UTC | settled (amount + payee) | 200 | 0x13a051a2…cacb | 978 ms |
| 40000 units (≈ $0.04 USDC) · L2 no_declarationWhose 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/f48b7c0f-473d-4338-b3cb-8d085c82fd5b)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.