feed-reader.bowling-anthony.workers.dev/feed
1.Catalog declaration
| Resource URL | https://feed-reader.bowling-anthony.workers.dev/feed |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x1831f336585a6c67b6a954d28f3e07f44c4eebbd |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-25 01:58 UTC / 2026-09-05 01:03 UTC |
| Catalog-reported calls / payers (30d) | 9 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-05 05:40 UTC | GET | pass | 402 | 484 ms | — |
| 2026-09-04 11:24 UTC | GET | fail | 402 | 109 ms | price_mismatch |
3.L1 — real purchases
0 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 4xx or 5xx counts as settled and not as delivered — definitions.
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-05 07:002026-09-05 07:00 UTC | settle_failed | 400 | — | 165 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checked | ||||
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.