api.predictionmarketdata.io/prediction-markets/pmcs-stats
1.Catalog declaration
| Resource URL | https://api.predictionmarketdata.io/prediction-markets/pmcs-stats |
| 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:52 UTC / 2026-10-03 01:04 UTC |
| Catalog-reported calls / payers (30d) | 7 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-03 16:40 UTC | GET | pass | 402 | 1973 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 512 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 119 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 2106 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 555 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 2895 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 3752 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 2368 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 132 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 551 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 3449 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 384 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 288 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 595 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 3614 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 73 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 677 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 3432 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 3795 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 3881 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 3626 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 445 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 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-20 18:012026-09-20 18:01 UTC | settled (nonce-bound) | 200 | 0x6816342f…6d6e | 8768 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-11 18:012026-09-11 18:01 UTC | settled (nonce-bound) | 200 | 0x61e8782f…70c8 | 1961 ms |
| 1000 units (≈ $0.001 USDC) · L2 mismatchWhose side: no failure (delivered) | ||||
| 09-02 01:002026-09-02 01:00 UTC | settled (amount + payee) | 200 | 0x8d3ed9a2…a828 | 8560 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 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/241dcb6c-efb8-41da-a58e-d6a1c1fae215)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-28 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-27 | 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.