polynews.news/api/v1/arbitrage
1.Catalog declaration
| Resource URL | https://polynews.news/api/v1/arbitrage |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x6ee49a7872844397fb52870cc07b308ffadc9427 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 391 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 291 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 230 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 398 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 570 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 304 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 255 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 308 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 1226 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 304 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 1830 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 408 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 406 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 325 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 668 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 73 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 291 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 2085 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 155 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 141 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 592 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 471 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 212 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled on-chain, and 4 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 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-16 00:012026-09-16 00:01 UTC | settled (nonce-bound) | 200 | 0xac86c646…0711 | 3606 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-29 12:072026-08-29 12:07 UTC | settled (amount + payee) | 200 | 0x037853ad…fb3f | 3375 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-20 12:572026-08-20 12:57 UTC | settled (amount + payee) | 200 | 0xe2d63786…1252 | 3644 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-14 09:572026-08-14 09:57 UTC | settled (amount + payee) | 200 | 0x7a39b8b8…000d | 6490 ms |
| 10000 units (≈ $0.01 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 4/4 settled · 4 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/ce7d3b83-157c-4fcc-b03d-46c80a5f84fa)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.