vendsdk.com/api/v/crypto-prices
1.Catalog declaration
| Resource URL | https://vendsdk.com/api/v/crypto-prices |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc648116b5debe4af7d78838aa468d07e0a9ab697 |
| Declared price (base units) | 5000 |
| Catalog status | active |
| First seen / last seen | 2026-08-21 01:57 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 2 / 2 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-18 16:40 UTC | GET | pass | 402 | 139 ms | — |
| 2026-10-17 13:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-10-15 21:40 UTC | GET | pass | 402 | 64 ms | — |
| 2026-10-14 15:40 UTC | GET | pass | 402 | 115 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 82 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 73 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-10-10 03:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-10-08 22:40 UTC | GET | pass | 402 | 164 ms | — |
| 2026-10-07 22:40 UTC | GET | pass | 402 | 201 ms | — |
| 2026-10-06 22:40 UTC | GET | pass | 402 | 107 ms | — |
| 2026-10-05 22:40 UTC | GET | pass | 402 | 136 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 214 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 228 ms | — |
| 2026-10-02 04:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 548 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 188 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 185 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 177 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 2266 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 225 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 290 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 346 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 237 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 801 ms | — |
| 2026-09-21 16:40 UTC | GET | pass | 402 | 715 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-24 18:022026-09-24 18:02 UTC | settled (nonce-bound) | 200 | 0xdf9a6e3b…f2d6 | 1545 ms |
| 5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-17 15:262026-09-17 15:26 UTC | settled (nonce-bound) | 200 | 0xf2d7120d…e53e | 1624 ms |
| 5000 units (≈ $0.005 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-11 06:002026-09-11 06:00 UTC | settled (nonce-bound) | 200 | 0xa83e5c90…3b2e | 1083 ms |
| 5000 units (≈ $0.005 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/600595a3-8b4b-47b4-ae1d-02960fa8f4c8)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.