oblique.markets/api/v1/paid/bazaar-pulse
1.Catalog declaration
| Resource URL | https://oblique.markets/api/v1/paid/bazaar-pulse |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x970007590acc5c938cd51345b17af51b1b40d3ab |
| Declared price (base units) | 2000 |
| 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 / 0 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-27 13:40 UTC | GET | pass | 402 | 407 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 313 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 366 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 303 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 356 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 435 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 2072 ms | — |
| 2026-09-20 22:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-09-20 04:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-19 13:40 UTC | GET | pass | 402 | 229 ms | — |
| 2026-09-18 16:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 144 ms | — |
| 2026-09-17 13:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-16 16:40 UTC | GET | pass | 402 | 393 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 2314 ms | — |
| 2026-09-15 04:40 UTC | GET | pass | 402 | 199 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 685 ms | — |
| 2026-09-13 22:40 UTC | GET | pass | 402 | 434 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 303 ms | — |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 259 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 205 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 447 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 709 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 385 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 138 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 86 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 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-10 01:012026-09-10 01:01 UTC | settled (nonce-bound) | 200 | 0xadbcbb33…93ae | 1532 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-27 12:312026-08-27 12:31 UTC | settled (amount + payee) | 200 | 0xe6c03523…b06c | 1486 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-20 12:562026-08-20 12:56 UTC | settled (amount + payee) | 200 | 0x283aea14…3f3f | 1092 ms |
| 2000 units (≈ $0.002 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 08-14 10:032026-08-14 10:03 UTC | settled (amount + payee) | 200 | 0x08283a7f…b1c4 | 1322 ms |
| 2000 units (≈ $0.002 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/70be9218-1b21-4cb1-96f0-62301880244f)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.