www.balticdryindex.com/v1/signals
1.Catalog declaration
| Resource URL | https://www.balticdryindex.com/v1/signals |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | base |
| Receiving address | 0xc58f8eff2b6f46b9f5e75432fcdebd5dd949b09f |
| Declared price (base units) | — |
| Catalog status | active |
| First seen / last seen | 2026-08-30 01:02 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 506 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 668 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 576 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 495 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 404 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 414 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 458 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 690 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 484 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 493 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 437 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 446 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 781 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 271 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 247 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 156 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 373 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 448 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 492 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 681 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 176 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 453 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 477 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.
L2 no_declaration- the listing's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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-23 00:022026-09-23 00:02 UTC | settled (nonce-bound) | 200 | 0x0bc3f4ff…e8f9 | 1063 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-15 23:502026-09-15 23:50 UTC | settled (nonce-bound) | 200 | 0x1212ea90…0e62 | 1305 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-09 01:002026-09-09 01:00 UTC | settled (nonce-bound) | 200 | 0xcf27a945…edca | 1150 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose 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/cbeaa0f0-4c11-49b6-bf9c-0bf22bc2e4d0)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.