api.delx.ai/api/v1/x402/data-classification
1.Catalog declaration
| Resource URL | https://api.delx.ai/api/v1/x402/data-classification |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x9f8bd9875b3e0b632a24a3a7c73f7787175e73a2 |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | POST | pass | 402 | 436 ms | — |
| 2026-10-18 13:40 UTC | POST | pass | 402 | 318 ms | — |
| 2026-10-17 04:40 UTC | POST | pass | 402 | 579 ms | — |
| 2026-10-15 15:40 UTC | POST | pass | 402 | 466 ms | — |
| 2026-10-14 12:40 UTC | POST | pass | 402 | 791 ms | — |
| 2026-10-12 21:40 UTC | POST | pass | 402 | 342 ms | — |
| 2026-10-11 21:40 UTC | POST | pass | 402 | 2364 ms | — |
| 2026-10-10 21:40 UTC | POST | pass | 402 | 355 ms | — |
| 2026-10-09 21:40 UTC | POST | pass | 402 | 339 ms | — |
| 2026-10-08 16:40 UTC | POST | pass | 402 | 330 ms | — |
| 2026-10-07 16:40 UTC | POST | pass | 402 | 459 ms | — |
| 2026-10-06 16:40 UTC | POST | pass | 402 | 421 ms | — |
| 2026-10-05 04:40 UTC | POST | pass | 402 | 2327 ms | — |
| 2026-10-04 13:40 UTC | POST | pass | 402 | 472 ms | — |
| 2026-10-03 16:40 UTC | POST | pass | 402 | 481 ms | — |
| 2026-10-02 16:40 UTC | POST | pass | 402 | 389 ms | — |
| 2026-10-01 22:40 UTC | POST | pass | 402 | 522 ms | — |
| 2026-10-01 04:40 UTC | POST | pass | 402 | 860 ms | — |
| 2026-09-30 13:40 UTC | POST | pass | 402 | 451 ms | — |
| 2026-09-29 16:40 UTC | POST | pass | 402 | 493 ms | — |
| 2026-09-28 22:40 UTC | POST | pass | 402 | 313 ms | — |
| 2026-09-28 04:40 UTC | POST | pass | 402 | 163 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 2203 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 456 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 318 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 339 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 283 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 296 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 1255 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 2276 ms | — |
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 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 |
|---|---|---|---|---|
| 09-21 00:022026-09-21 00:02 UTC | settled (nonce-bound) | 200 | 0x38fb03f4…c038 | 1786 ms |
| 3000 units (≈ $0.003 USDC) · L2 matchWhose 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/6101ee1b-f779-44f3-906a-8b10fc294b58)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-20 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-06 | 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.