x402.deepsearch.com/v1/context/crypto/market
1.Catalog declaration
| Resource URL | https://x402.deepsearch.com/v1/context/crypto/market |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xbecc987508adf6696a3254bed485cc2d9493c8ad |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-20 13:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 22:40 UTC | GET | pass | 402 | 2821 ms | — |
| 2026-10-18 13:40 UTC | GET | pass | 402 | 774 ms | — |
| 2026-10-17 04:40 UTC | GET | pass | 402 | 848 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 946 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 780 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 933 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 897 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 959 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 878 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 996 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 1063 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 984 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 765 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 757 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 806 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 911 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 763 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 816 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 934 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 2779 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 924 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 920 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 848 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 768 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 779 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 727 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 894 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 901 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 796 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 815 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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's output schema gave vet402 nothing to check this response against (no schema, a schema with no required keys and no example properties, or example properties with a content type that is not JSON). An output example the seller puts in the 402 (extensions.bazaar.info.output.example) is not checked yet.
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-15 23:502026-09-15 23:50 UTC | settled (nonce-bound) | 200 | 0x2908f5ea…8761 | 2151 ms |
| 50000 units (≈ $0.05 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-09 19:002026-09-09 19:00 UTC | settled (nonce-bound) | 200 | 0x4a8df7b8…958f | 2666 ms |
| 50000 units (≈ $0.05 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/aec4394f-2feb-4c4f-9200-b96d92950b01)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.