lionx402.com/api/x402/tx-receipt-decoded-json
1.Catalog declaration
| Resource URL | https://lionx402.com/api/x402/tx-receipt-decoded-json |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x68e3e7822cf83c824cf9606ec999b5e8a93c85b5 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-28 01:11 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 4 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-20 04:40 UTC | GET | pass | 402 | 663 ms | — |
| 2026-10-18 16:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 651 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 507 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 405 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 537 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 562 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 368 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 862 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 7532 ms | — |
| 2026-10-07 16:40 UTC | GET | pass | 402 | 475 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 2430 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 367 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 270 ms | — |
| 2026-10-03 16:40 UTC | GET | pass | 402 | 598 ms | — |
| 2026-10-02 22:40 UTC | GET | pass | 402 | 683 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 565 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 704 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 856 ms | — |
| 2026-09-29 16:40 UTC | GET | pass | 402 | 387 ms | — |
| 2026-09-28 22:40 UTC | GET | pass | 402 | 992 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 6666 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 216 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 754 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 560 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 973 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 240 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 1027 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 575 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 585 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 01:002026-09-07 01:00 UTC | settled (nonce-bound) | 200 | 0x204eda10…d118 | 1874 ms |
| 10000 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/13d39cdf-7346-41cf-9d57-5229fd13ccd1)4.Catalog listing events
No listing changes observed.
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.