vending-machine-seven.vercel.app/api/v/fx-rate
1.Catalog declaration
| Resource URL | https://vending-machine-seven.vercel.app/api/v/fx-rate |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xc648116b5debe4af7d78838aa468d07e0a9ab697 |
| Declared price (base units) | 3000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:52 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 3 / 3 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-15 15:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 249 ms | — |
| 2026-10-13 03:40 UTC | GET | pass | 402 | 96 ms | — |
| 2026-10-12 03:40 UTC | GET | pass | 402 | 294 ms | — |
| 2026-10-11 03:40 UTC | GET | pass | 402 | 241 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 3980 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 2086 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 79 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 288 ms | — |
| 2026-10-04 22:40 UTC | GET | pass | 402 | 206 ms | — |
| 2026-10-04 04:40 UTC | GET | pass | 402 | 242 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 258 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 239 ms | — |
| 2026-10-01 16:40 UTC | GET | pass | 402 | 61 ms | — |
| 2026-09-30 22:40 UTC | GET | pass | 402 | 75 ms | — |
| 2026-09-30 04:40 UTC | GET | pass | 402 | 243 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 324 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 202 ms | — |
| 2026-09-27 22:40 UTC | GET | pass | 402 | 202 ms | — |
| 2026-09-27 04:40 UTC | GET | pass | 402 | 2142 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 458 ms | — |
| 2026-09-25 16:40 UTC | GET | pass | 402 | 51 ms | — |
| 2026-09-24 22:40 UTC | GET | pass | 402 | 72 ms | — |
| 2026-09-24 04:40 UTC | GET | pass | 402 | 2057 ms | — |
| 2026-09-23 13:40 UTC | GET | pass | 402 | 646 ms | — |
| 2026-09-22 16:40 UTC | GET | pass | 402 | 155 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 74 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 92 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 121 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.
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 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 15:242026-09-17 15:24 UTC | settled (nonce-bound) | 200 | 0xa217daee…69ea | 1284 ms |
| 3000 units (≈ $0.003 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-11 12:092026-09-11 12:09 UTC | settled (nonce-bound) | 200 | 0x9370d510…b2d9 | 1282 ms |
| 3000 units (≈ $0.003 USDC) · L2 matchWhose side: no failure (delivered) | ||||
| 09-02 19:022026-09-02 19:02 UTC | settled (amount + payee) | 200 | 0x01f5b847…560a | 1409 ms |
| 3000 units (≈ $0.003 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/827c7c0b-6802-4fb3-affa-ca40de2ade2d)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-11 | relisted | {"status":"delisted"} | {"status":"active"} |
| 2026-10-10 | 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.