oracle.the-undesirables.com/api/v1/market
1.Catalog declaration
| Resource URL | https://oracle.the-undesirables.com/api/v1/market |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x642e8a7c289381f24f0395e0539f0ba41c74cc1b |
| Declared price (base units) | 25000 |
| Catalog status | delisted (since 2026-09-21 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-20 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-20 22:40 UTC | GET | fail | 200 | 353 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-20 04:40 UTC | GET | fail | 530 | 401 ms | no_402HTTP 530 instead of 402 to an unpaid GET. |
| 2026-09-19 13:40 UTC | GET | fail | 200 | 281 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-18 16:40 UTC | GET | fail | 200 | 138 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-18 04:40 UTC | GET | fail | 200 | 381 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-17 13:40 UTC | GET | fail | 200 | 215 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-16 16:40 UTC | GET | fail | 200 | 179 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-15 22:40 UTC | GET | fail | 200 | 250 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-15 04:40 UTC | GET | fail | 200 | 196 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-14 13:40 UTC | GET | fail | 200 | 220 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-13 22:40 UTC | GET | fail | 200 | 191 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-13 04:40 UTC | GET | fail | 200 | 428 ms | no_402HTTP 200 instead of 402 to an unpaid GET. |
| 2026-09-12 16:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 233 ms | — |
| 2026-09-10 23:40 UTC | GET | pass | 402 | 205 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 319 ms | — |
| 2026-09-09 05:40 UTC | GET | pass | 402 | 2121 ms | — |
| 2026-09-08 17:40 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-08 05:40 UTC | GET | pass | 402 | 296 ms | — |
| 2026-09-07 17:40 UTC | GET | pass | 402 | 203 ms | — |
| 2026-09-06 23:40 UTC | GET | pass | 402 | 2011 ms | — |
| 2026-09-06 14:40 UTC | GET | pass | 402 | 2159 ms | — |
| 2026-09-05 23:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-09-05 14:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-09-04 23:40 UTC | GET | pass | 402 | 316 ms | — |
| 2026-09-04 14:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-03 23:40 UTC | GET | pass | 402 | 257 ms | — |
| 2026-09-03 14:40 UTC | GET | pass | 402 | 286 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 (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 match- the response had the 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 |
|---|---|---|---|---|
| 08-30 12:092026-08-30 12:09 UTC | settled (amount + payee) | 200 | 0xc2f0784a…950b | 12271 ms |
| 25000 units (≈ $0.03 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-21 08:322026-08-21 08:32 UTC | settled (amount + payee) | 200 | 0xf0711dc9…cdfe | 2093 ms |
| 25000 units (≈ $0.03 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 08-14 10:032026-08-14 10:03 UTC | settled (amount + payee) | 200 | 0xf0f4a9a0…b9bf | 9345 ms |
| 25000 units (≈ $0.03 USDC) · L2 matchWhose 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/d07d5543-572f-46d7-822c-7356ad00b284)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-21 | 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.