api.predictionmarketdata.io/prediction-markets/similar
1.Catalog declaration
| Resource URL | https://api.predictionmarketdata.io/prediction-markets/similar |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x995c0abdcd2ad76548e5f7deb54d32549b2b781f |
| Declared price (base units) | 5000 |
| Catalog status | delisted (since 2026-09-28 01:02 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-27 01:02 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-26 16:40 UTC | GET | pass | 402 | 599 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 431 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 2070 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 143 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 333 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 90 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 135 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 837 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 3952 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 41 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 623 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 3883 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 4014 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 3263 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 3581 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 94 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 146 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 3364 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 26 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 54 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 3661 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 3199 ms | — |
| 2026-09-07 05:40 UTC | GET | pass | 402 | 533 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 (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 |
|---|---|---|---|---|
| 08-25 12:532026-08-25 12:53 UTC | settled (amount + payee) | 200 | 0x0d757c18…a8f1 | 4508 ms |
| 5000 units (≈ $0.005 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-19 12:122026-08-19 12:12 UTC | settled (amount + payee) | 200 | 0x0f537d42…02ad | 6159 ms |
| 5000 units (≈ $0.005 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/91294c58-2cb9-4e1e-9a5d-66eebdcc1757)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-28 | delisted | {"status":"active"} | {"status":"delisted"} |
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.