signal.keelbase.io/api/v1/daily/latest
1.Catalog declaration
| Resource URL | https://signal.keelbase.io/api/v1/daily/latest |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x7b177b724d6b02f69d9f25d9b91c63338c554dbf |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 505 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 240 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 1427 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 247 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 155 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 1183 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 1701 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 385 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 632 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 419 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 229 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 148 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 122 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 478 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 615 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 1514 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 1991 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 2150 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 1002 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 319 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.
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 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 15:242026-09-17 15:24 UTC | settled (nonce-bound) | 200 | 0xcf2f4bd1…4c00 | 1130 ms |
| 30000 units (≈ $0.03 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered) | ||||
| 09-11 12:092026-09-11 12:09 UTC | settled (nonce-bound) | 200 | 0x7053e949…d820 | 1796 ms |
| 30000 units (≈ $0.03 USDC) · L2 not_checked (recorded mismatch)Whose side: no failure (delivered) | ||||
| 09-02 12:092026-09-02 12:09 UTC | settled (amount + payee) | 200 | 0xa5673b82…fb99 | 1156 ms |
| 30000 units (≈ $0.03 USDC) · L2 not_checked (recorded mismatch)Whose 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/6f9fe4b9-f474-4f6d-8c74-9b74c61bba36)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"} |
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.