polynews.news/api/v1/feed
1.Catalog declaration
| Resource URL | https://polynews.news/api/v1/feed |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6ee49a7872844397fb52870cc07b308ffadc9427 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 16 / 8 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 22:40 UTC | GET | pass | 402 | 186 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 547 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 280 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 1063 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 453 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 101 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 54 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 2290 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 1421 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 1879 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 252 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 487 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 385 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 77 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 309 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 611 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 94 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 49 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 455 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 299 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 78 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 426 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 match- the response had the fields the listing's output schema declares.
L2 mismatch- the response lacked fields the listing's output schema declares.
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-12 00:002026-09-12 00:00 UTC | settled (nonce-bound) | 200 | 0x32fc9bab…c640 | 16810 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-23 12:422026-08-23 12:42 UTC | settled (amount + payee) | 200 | 0x6a19db5a…c048 | 16698 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-16 12:482026-08-16 12:48 UTC | settled (amount + payee) | 200 | 0x570be605…0633 | 16515 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose 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/200ad0e0-787b-4c05-81fc-915ca6576fae)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.