api.delx.ai/api/v1/x402/timestamp
1.Catalog declaration
| Resource URL | https://api.delx.ai/api/v1/x402/timestamp |
| Source | cdp_bazaar |
| Declared method | POST |
| Network | eip155:8453 |
| Receiving address | 0x9f8bd9875b3e0b632a24a3a7c73f7787175e73a2 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-13 01:02 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-13 10:30 UTC | POST | pass | 402 | 128 ms | — |
| 2026-09-27 13:40 UTC | POST | pass | 402 | 2038 ms | — |
| 2026-09-26 16:40 UTC | POST | pass | 402 | 325 ms | — |
| 2026-09-25 22:40 UTC | POST | pass | 402 | 162 ms | — |
| 2026-09-25 04:40 UTC | POST | pass | 402 | 2389 ms | — |
| 2026-09-24 13:40 UTC | POST | pass | 402 | 110 ms | — |
| 2026-09-23 16:40 UTC | POST | pass | 402 | 288 ms | — |
| 2026-09-22 22:40 UTC | POST | pass | 402 | 258 ms | — |
| 2026-09-22 04:40 UTC | POST | pass | 402 | 289 ms | — |
| 2026-09-21 13:40 UTC | POST | pass | 402 | 256 ms | — |
| 2026-09-20 16:40 UTC | POST | pass | 402 | 303 ms | — |
| 2026-09-20 04:40 UTC | POST | pass | 402 | 208 ms | — |
| 2026-09-19 13:40 UTC | POST | pass | 402 | 399 ms | — |
| 2026-09-18 16:40 UTC | POST | pass | 402 | 444 ms | — |
| 2026-09-17 22:40 UTC | POST | pass | 402 | 371 ms | — |
| 2026-09-17 04:40 UTC | POST | pass | 402 | 361 ms | — |
| 2026-09-16 16:40 UTC | POST | pass | 402 | 420 ms | — |
| 2026-09-15 16:40 UTC | POST | pass | 402 | 1330 ms | — |
| 2026-09-15 04:40 UTC | POST | pass | 402 | 475 ms | — |
| 2026-09-14 13:40 UTC | POST | pass | 402 | 2143 ms | — |
| 2026-09-13 16:40 UTC | POST | pass | 402 | 356 ms | — |
| 2026-09-13 04:40 UTC | POST | pass | 402 | 452 ms | — |
| 2026-09-12 16:40 UTC | POST | pass | 402 | 439 ms | — |
| 2026-09-11 22:40 UTC | POST | pass | 402 | 351 ms | — |
| 2026-09-11 13:40 UTC | POST | pass | 402 | 350 ms | — |
| 2026-09-10 17:40 UTC | POST | pass | 402 | 361 ms | — |
| 2026-09-10 05:40 UTC | POST | pass | 402 | 914 ms | — |
| 2026-09-09 17:40 UTC | POST | pass | 402 | 335 ms | — |
| 2026-09-09 05:40 UTC | POST | pass | 402 | 484 ms | — |
| 2026-09-08 14:40 UTC | POST | pass | 402 | 422 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 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-07 19:012026-09-07 19:01 UTC | settled (nonce-bound) | 200 | 0xbd53d4f3…fe38 | 1745 ms |
| 1000 units (≈ $0.001 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/227b6e85-e6f5-470d-9854-e8a592453d57)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-08 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-28 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-08-29 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-16 | 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.