mechamanda.com/api/polymarket/trending
1.Catalog declaration
| Resource URL | https://mechamanda.com/api/polymarket/trending |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xbad1aa224bfe4feb460e12b2553dcdf98a7098d0 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-02 01:04 UTC |
| Catalog-reported calls / payers (30d) | 4 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-02 16:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 81 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 449 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 274 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 99 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 84 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 423 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 2125 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 104 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 167 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 106 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 137 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 2237 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 100 ms | — |
| 2026-09-19 04:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-18 13:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 723 ms | — |
| 2026-09-17 04:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-09-16 13:40 UTC | GET | pass | 402 | 1002 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 2149 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 260 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 604 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 98 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 1466 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.
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-21 18:022026-09-21 18:02 UTC | settled (nonce-bound) | 200 | 0xb7d2b3d0…9f4f | 3238 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-11 18:012026-09-11 18:01 UTC | settled (nonce-bound) | 200 | 0x5861567e…c09a | 2618 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-04 12:082026-09-04 12:08 UTC | settled (nonce-bound) | 200 | 0x1e3f4a56…f6ce | 2028 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/306eacde-6de9-4f59-ab91-ea627c2b86c7)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.