402.com.tr/api/x402/chain-status
1.Catalog declaration
| Resource URL | https://402.com.tr/api/x402/chain-status |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x973a31858f4d2125f48c880542da11a2796f12d6 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 4 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | GET | pass | 402 | 596 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 375 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 349 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 587 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 1214 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 1232 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 693 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 739 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 506 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 344 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 456 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 354 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 598 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 563 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 468 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 382 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 562 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 346 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 361 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 475 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 494 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 340 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 697 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 568 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 376 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 538 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 374 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 425 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 598 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled with a receipt, and 2 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. 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.
settled (amount + payee)- vet402 confirmed the USDC transfer on-chain; the on-chain re-read matched amount, payee, asset and chain; no nonce was on record (rows before 2026-09-04).
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 | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-10 12:082026-09-10 12:08 UTC | settled (nonce-bound) | 200 | 0xe6e90cec…6c4d | 2385 ms |
| 10000 units (≈ $0.01 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-02 12:082026-09-02 12:08 UTC | settled (amount + payee) | 200 | 0xa6f9655a…6b3a | 2795 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 2/2 settled · 2 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/8542e9f0-5ce4-46af-a5c0-480a7e024c21)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.
About the purchase at 2026-09-10T12:08:58Z (UTC). The form starts with that time; add what you saw instead.