api.speccy.cloud/v1/predictions/polymarket
1.Catalog declaration
| Resource URL | https://api.speccy.cloud/v1/predictions/polymarket |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x0cb12df486381a0ebebc0ef338da80657f68f9cb |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-24 02:00 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 9 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 472 ms | — |
| 2026-10-18 16:40 UTC | GET | pass | 402 | 556 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 506 ms | — |
| 2026-10-15 15:40 UTC | GET | pass | 402 | 345 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 678 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 419 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 481 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 385 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 337 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 5104 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 934 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 820 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 781 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 380 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 641 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 377 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 563 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 412 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 772 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 306 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 1901 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 457 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 366 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 386 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 310 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 1674 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-18 18:022026-09-18 18:02 UTC | settled (nonce-bound) | 200 | 0x333463cf…75c3 | 2091 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-12 12:082026-09-12 12:08 UTC | settled (nonce-bound) | 200 | 0x0b764979…fee8 | 1580 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-03 01:012026-09-03 01:01 UTC | settled (amount + payee) | 200 | 0x0ace395c…ad5d | 1619 ms |
| 10000 units (≈ $0.01 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/dd547e3a-2dc5-4e65-91a0-f58dcedf75b3)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.