tools.halowerk.com/v1/news/feed
1.Catalog declaration
| Resource URL | https://tools.halowerk.com/v1/news/feed |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x2880edfff13100677bf97a3cbdf3bc34771c4e5e |
| Declared price (base units) | 2000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | POST | pass | 402 | 417 ms | — |
| 2026-10-18 04:40 UTC | POST | pass | 402 | 722 ms | — |
| 2026-10-16 21:40 UTC | POST | pass | 402 | 422 ms | — |
| 2026-10-15 12:40 UTC | POST | pass | 402 | 278 ms | — |
| 2026-10-13 15:40 UTC | POST | pass | 402 | 380 ms | — |
| 2026-10-12 12:40 UTC | POST | pass | 402 | 408 ms | — |
| 2026-10-11 12:40 UTC | POST | pass | 402 | 334 ms | — |
| 2026-10-10 12:40 UTC | POST | pass | 402 | 315 ms | — |
| 2026-10-09 12:40 UTC | POST | pass | 402 | 233 ms | — |
| 2026-10-07 22:40 UTC | POST | pass | 402 | 400 ms | — |
| 2026-10-07 04:40 UTC | POST | pass | 402 | 696 ms | — |
| 2026-09-15 22:40 UTC | POST | pass | 402 | 2111 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 240 ms | — |
| 2026-09-14 16:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-13 22:40 UTC | POST | pass | 402 | 128 ms | — |
| 2026-09-13 13:40 UTC | POST | pass | 402 | 345 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 163 ms | — |
| 2026-09-12 04:40 UTC | POST | pass | 402 | 398 ms | — |
| 2026-09-11 16:40 UTC | POST | pass | 402 | 353 ms | — |
| 2026-09-10 23:40 UTC | POST | pass | 402 | 478 ms | — |
| 2026-09-10 14:40 UTC | POST | pass | 402 | 353 ms | — |
| 2026-09-09 23:40 UTC | POST | pass | 402 | 410 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 481 ms | — |
| 2026-09-08 17:40 UTC | POST | pass | 402 | 674 ms | — |
| 2026-09-08 05:40 UTC | POST | pass | 402 | 351 ms | — |
| 2026-09-07 17:40 UTC | POST | pass | 402 | 148 ms | — |
| 2026-09-07 05:40 UTC | POST | pass | 402 | 385 ms | — |
| 2026-09-06 17:40 UTC | POST | pass | 402 | 443 ms | — |
| 2026-09-06 05:40 UTC | POST | pass | 402 | 347 ms | — |
| 2026-09-05 17:40 UTC | POST | pass | 402 | 326 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'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 |
|---|---|---|---|---|
| 08-14 10:112026-08-14 10:11 UTC | settled (amount + payee) | 200 | 0x45b89b09…fde2 | 1502 ms |
| 2000 units (≈ $0.002 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/a72f0c3a-a290-4acf-9014-ef882d373b94)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-07 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-16 | 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.