api.x402node.dev/market/options-max-pain
1.Catalog declaration
| Resource URL | https://api.x402node.dev/market/options-max-pain |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x4466d4a84b7c49a6a094ec6eef4a0712d6dd125e |
| Declared price (base units) | 15000 |
| Catalog status | delisted (since 2026-09-17 01:03 UTC) |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-09-16 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-16 13:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-09-15 16:40 UTC | GET | pass | 402 | 279 ms | — |
| 2026-09-14 22:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-09-14 13:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-09-13 16:40 UTC | GET | pass | 402 | 368 ms | — |
| 2026-09-13 04:40 UTC | GET | pass | 402 | 298 ms | — |
| 2026-09-12 13:40 UTC | GET | pass | 402 | 310 ms | — |
| 2026-09-11 22:40 UTC | GET | pass | 402 | 204 ms | — |
| 2026-09-11 13:40 UTC | GET | pass | 402 | 302 ms | — |
| 2026-09-10 17:40 UTC | GET | pass | 402 | 68 ms | — |
| 2026-09-10 05:40 UTC | GET | pass | 402 | 277 ms | — |
| 2026-09-09 17:40 UTC | GET | pass | 402 | 229 ms | — |
| 2026-09-08 23:40 UTC | GET | pass | 402 | 264 ms | — |
| 2026-09-08 14:40 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-07 23:40 UTC | GET | pass | 402 | 320 ms | — |
| 2026-09-07 14:40 UTC | GET | pass | 402 | 197 ms | — |
| 2026-09-06 23:40 UTC | GET | pass | 402 | 188 ms | — |
| 2026-09-06 14:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-09-05 23:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-05 14:40 UTC | GET | pass | 402 | 69 ms | — |
| 2026-09-04 23:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-09-04 14:40 UTC | GET | pass | 402 | 105 ms | — |
| 2026-09-03 23:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-03 14:40 UTC | GET | pass | 402 | 71 ms | — |
| 2026-09-02 23:40 UTC | GET | pass | 402 | 71 ms | — |
| 2026-09-02 14:40 UTC | GET | pass | 402 | 151 ms | — |
| 2026-09-01 11:24 UTC | GET | fail | 402 | 62 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
1 of 1 paid attempts settled on-chain, and 1 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-06 01:022026-09-06 01:02 UTC | settled (nonce-bound) | 200 | 0x98ceabc6…066e | 2405 ms |
| 15000 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 1/1 settled · 1 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/677311ef-1e72-4808-b623-374861623a96)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-17 | 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.