polymarket-signal-api.pwnker-polymarket-signals.workers.dev/v1/performance
1.Catalog declaration
| Resource URL | https://polymarket-signal-api.pwnker-polymarket-signals.workers.dev/v1/performance |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x338d8649efa45b940d6656030faa58d9d01e6983 |
| 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) | 7 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 04:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 493 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 256 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 521 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 447 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 293 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 230 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 130 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 178 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 443 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 362 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 272 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 244 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 280 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 364 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 179 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 182 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 10 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 11 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 439 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 477 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 38 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 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-17 12:542026-09-17 12:54 UTC | settled (nonce-bound) | 200 | 0xae0e65c1…17ed | 1534 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-11 01:012026-09-11 01:01 UTC | settled (nonce-bound) | 200 | 0xe5e4d981…4054 | 1096 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-03 07:012026-09-03 07:01 UTC | settled (amount + payee) | 200 | 0x911d5bcb…92e3 | 1072 ms |
| 1000 units (≈ $0.001 USDC) · L2 no_declarationWhose 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/d6431d7e-7e85-4a86-9cd3-c182e6033bdb)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.