api.x-402.online/v1/extract
1.Catalog declaration
| Resource URL | https://api.x-402.online/v1/extract |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x2c871c2b8876dc35e9e19646fda5abf1cd27735f |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-01 01:03 UTC |
| Catalog-reported calls / payers (30d) | 5 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-01 04:40 UTC | POST | pass | 402 | 155 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 129 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 93 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 79 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 45 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 175 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 127 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 359 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 66 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 1941 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 219 ms | — |
| 2026-09-23 04:40 UTC | POST | pass | 402 | 75 ms | — |
| 2026-09-22 13:40 UTC | POST | pass | 402 | 172 ms | — |
| 2026-09-21 16:40 UTC | POST | pass | 402 | 243 ms | — |
| 2026-09-20 22:40 UTC | POST | pass | 402 | 240 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 676 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 292 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 108 ms | — |
| 2026-09-18 04:40 UTC | POST | pass | 402 | 149 ms | — |
| 2026-09-03 17:40 UTC | POST | pass | 402 | 138 ms | — |
| 2026-09-03 05:40 UTC | POST | pass | 402 | 88 ms | — |
| 2026-09-02 23:40 UTC | POST | pass | 402 | 205 ms | — |
| 2026-08-24 11:11 UTC | POST | pass | 402 | 135 ms | — |
3.L1 — real purchases
1 of 2 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
settle_claimed- the seller returned a receipt that vet402 has not re-read on-chain yet.
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 |
|---|---|---|---|---|
| 10-01 12:022026-10-01 12:02 UTC | settle_claimed | 200 | 0x598fedd8…42bd | 1148 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: not sorted: awaiting on-chain verification | ||||
| 09-19 12:082026-09-19 12:08 UTC | settled (nonce-bound) | 200 | 0xd3872e82…4ff9 | 4359 ms |
| 5000 units (≈ $0.005 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/2 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/e31f4799-84c1-4eb2-966e-1d3b9443ca6c)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-18 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-04 | 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.