x402-trends-server.onrender.com/api/crypto-market
1.Catalog declaration
| Resource URL | https://x402-trends-server.onrender.com/api/crypto-market |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xf61f957d9ac432309219549b1ae79ae8b7c71ff5 |
| Declared price (base units) | 50000 |
| Catalog status | active |
| First seen / last seen | 2026-08-17 01:06 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 6 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 2037 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 159 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 184 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 147 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 166 ms | — |
| 2026-10-10 15:40 UTC | GET | pass | 402 | 803 ms | — |
| 2026-10-09 15:40 UTC | GET | pass | 402 | 218 ms | — |
| 2026-10-08 13:40 UTC | GET | pass | 402 | 220 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 304 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 2142 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 2118 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 222 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 78 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 2028 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 210 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 407 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 193 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 646 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 134 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 60 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 128 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 187 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 2334 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 370 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 155 ms | — |
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 |
|---|---|---|---|---|
| 09-17 18:012026-09-17 18:01 UTC | settled (nonce-bound) | 200 | 0x6d703d60…02c0 | 957 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-11 12:092026-09-11 12:09 UTC | settled (nonce-bound) | 200 | 0x8495cbf8…bd39 | 694 ms |
| 50000 units (≈ $0.05 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-04 12:082026-09-04 12:08 UTC | settled (nonce-bound) | 200 | 0x21bb58aa…7e2c | 661 ms |
| 50000 units (≈ $0.05 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/3a04c33d-6e99-4064-b2c6-0e47593550d5)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.