x402.ochinimus.app/api/trade-context
1.Catalog declaration
| Resource URL | https://x402.ochinimus.app/api/trade-context |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp |
| Receiving address | 4a8o45skRPcyjAdyR8yES215Swvh8uTpZD6KLarhxCJ7 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 4 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 403 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 352 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 2225 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 432 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 1037 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 129 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 426 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 379 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 223 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 422 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 297 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 725 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 483 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 466 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 587 ms | — |
| 2026-10-01 10:30 UTC | GET | pass | 402 | 146 ms | — |
| 2026-09-26 10:30 UTC | GET | pass | 402 | 207 ms | — |
| 2026-09-18 11:24 UTC | GET | pass | 402 | 326 ms | — |
| 2026-09-15 11:24 UTC | GET | pass | 402 | 374 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 350 ms | — |
| 2026-09-08 11:24 UTC | GET | pass | 402 | 156 ms | — |
| 2026-09-03 11:24 UTC | GET | pass | 402 | 500 ms | — |
| 2026-08-27 10:33 UTC | GET | fail | 402 | 326 ms | accepts_invalid402 without a payable accept in the header or the body (which part was missing was not recorded before the 2026-09-29 change). |
3.L1 — real purchases
3 of 3 paid attempts settled on-chain, and 3 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 |
|---|---|---|---|---|
| 10-15 05:002026-10-15 05:00 UTC | settled (nonce-bound) | 200 | UqpegkSNMv…MnMj | 3802 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 10-08 09:302026-10-08 09:30 UTC | settled (nonce-bound) | 200 | 5kYwvJHUSw…FikU | 3503 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 10-02 06:002026-10-02 06:00 UTC | settled (nonce-bound) | 200 | 21WegPW7Jx…XdeD | 2043 ms |
| 10000 units (≈ $0.01 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 3/3 settled · 3 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/c8bce8a3-edd9-4630-8440-805d8d9c5c86)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-09-26 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-09-22 | delisted | {"status":"active"} | {"status":"delisted"} |
| 2026-08-23 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-08-19 | 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.