api.predictionmarketdata.io/prediction-markets
1.Catalog declaration
| Resource URL | https://api.predictionmarketdata.io/prediction-markets |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x995c0abdcd2ad76548e5f7deb54d32549b2b781f |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-30 01:03 UTC |
| Catalog-reported calls / payers (30d) | 5 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-30 04:40 UTC | GET | pass | 402 | 374 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 661 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 489 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 91 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 3202 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 81 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 169 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 108 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 215 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 210 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 168 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 89 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 149 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 3441 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 2153 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 334 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 43 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 753 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 111 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 289 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 2984 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-10 01:012026-09-10 01:01 UTC | settled (nonce-bound) | 200 | 0xaeca11c6…20b5 | 6767 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-31 12:082026-08-31 12:08 UTC | settled (amount + payee) | 200 | 0x9ecff6bf…c087 | 5125 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-21 08:312026-08-21 08:31 UTC | settled (amount + payee) | 200 | 0x62636599…bb9d | 9199 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 08-14 10:022026-08-14 10:02 UTC | settled (amount + payee) | 200 | 0xa81c99b0…ceff | 2684 ms |
| 1000 units (≈ $0.001 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/a7284c79-72d6-401e-a650-8c8a054970ba)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.