api.x402node.dev/web/og
1.Catalog declaration
| Resource URL | https://api.x402node.dev/web/og |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x4466d4a84b7c49a6a094ec6eef4a0712d6dd125e |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-07 13:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-07 04:40 UTC | GET | pass | 402 | 120 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 63 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 78 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 251 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 1967 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 227 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 200 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 332 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 321 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 369 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 237 ms | — |
| 2026-09-22 11:24 UTC | GET | pass | 402 | 65 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-16 11:24 UTC | GET | pass | 402 | 60 ms | — |
| 2026-09-12 11:24 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-01 11:24 UTC | GET | fail | 402 | 66 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
0 of 2 paid attempts settled on-chain, and 0 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
settle_failed- vet402 signed a payment and got no settlement receipt back.
L2 not_checked- not checked: the paid request did not answer 200, so there was no response to check against the listing's output schema.
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 |
|---|---|---|---|---|
| 10-02 15:322026-10-02 15:32 UTC | settle_failed | 500 | — | 541 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: one failure so far | ||||
| 09-26 06:002026-09-26 06:00 UTC | settle_failed | 500 | — | 683 ms |
| 5000 units (≈ $0.005 USDC) · L2 not_checkedWhose side: not sorted: vet402 unproven | ||||
4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-08-31 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-25 | 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.