api.oblique.markets/api/v1/paid/bazaar-trending
1.Catalog declaration
| Resource URL | https://api.oblique.markets/api/v1/paid/bazaar-trending |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x970007590acc5c938cd51345b17af51b1b40d3ab |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:02 UTC |
| Catalog-reported calls / payers (30d) | 6 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-28 22:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 55 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 219 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 314 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 2134 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 175 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 468 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 2235 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-09-17 22:40 UTC | GET | pass | 402 | 331 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 100 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 45 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 1832 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 114 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 1730 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 263 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 54 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 154 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 553 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 197 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 215 ms | — |
3.L1 — real purchases
4 of 4 paid attempts settled with a receipt, and 4 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-11 12:082026-09-11 12:08 UTC | settled (nonce-bound) | 200 | 0x551c34ea…995d | 1419 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-29 12:072026-08-29 12:07 UTC | settled (amount + payee) | 200 | 0x2bff4fc6…c766 | 884 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-21 12:212026-08-21 12:21 UTC | settled (amount + payee) | 200 | 0x760c7ec7…f851 | 1217 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-14 10:112026-08-14 10:11 UTC | settled (amount + payee) | 200 | 0x20b247c4…18c3 | 818 ms |
| 3000 units (≈ $0.003 USDC) · L2 no_declarationWhose 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/ae282bc2-526f-4e42-9e89-95314edf29c0)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.
About the purchase at 2026-08-29T12:07:49Z (UTC). The form starts with that time; add what you saw instead.