odds.rjhsignaltech.workers.dev/v1/consensus
1.Catalog declaration
| Resource URL | https://odds.rjhsignaltech.workers.dev/v1/consensus |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x2e8dfc2a77adcdd865a46293844c250462a1c32d |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-09-25 01:02 UTC / 2026-09-27 01:02 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-27 04:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 529 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 583 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 292 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 0 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
1 of those paid attempts are held as inconclusive rather than counted against this seller (1 settled and answered 4xx, 0 answered 4xx with no settlement receipt, 0 answered 402 or 5xx while our own payer wallet was out of USDC, 2026-09-13 00:00 to 2026-09-15 23:49 UTC). A 4xx says the request was not one the server would accept, and we cannot rule out that the request was ours to get wrong: vet402 buys with no API key of the seller's, and sends a POST body only when the seller declares one. This is the same principle the methodology already applied to path_template URLs, applied to the body and the authentication header as well. The rows are not deleted and not hidden — they are below, with their status and HTTP code, and they are out of the denominator for delivered (corrections).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-25 12:012026-09-25 12:01 UTC | settled (nonce-bound) | 400 | 0x78bb43af…764c | 1108 ms |
| 10000 units (≈ $0.01 USDC) · L2 not_checked | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 0 delivered · 1 inconclusive 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/740c7c7d-a887-430b-9f16-f4fa6727be15)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.