polymarket-signal-api.pwnker-polymarket-signals.workers.dev/v1/markets/rank
1.Catalog declaration
| Resource URL | https://polymarket-signal-api.pwnker-polymarket-signals.workers.dev/v1/markets/rank |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x338d8649efa45b940d6656030faa58d9d01e6983 |
| Declared price (base units) | 30000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 5 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 254 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 338 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 226 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 9103 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 353 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 316 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 421 ms | — |
| 2026-10-05 22:40 UTC | GET | pass | 402 | 418 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 368 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 342 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 648 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 474 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 243 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 539 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 479 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 210 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 334 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 220 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 221 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 283 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 528 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 240 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 288 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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.
L2 no_declaration- the listing declares no output schema to check the response against.
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 | 0x8e079b32…8ae5 | 1325 ms |
| 30000 units (≈ $0.03 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-09 19:002026-09-09 19:00 UTC | settled (nonce-bound) | 200 | 0xb5a4b4e1…411b | 1401 ms |
| 30000 units (≈ $0.03 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 2/2 settled · 2 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/eb59cae3-3630-44b8-aff4-50a577cd3212)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.