x402.ottoai.services/fx-rates
1.Catalog declaration
| Resource URL | https://x402.ottoai.services/fx-rates |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x0e84ddedaae6a779c462c22a59f301ec31b6b808 |
| Declared price (base units) | 1000 |
| Catalog status | active |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-21 01:01 UTC |
| Catalog-reported calls / payers (30d) | 11 / 8 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-21 04:40 UTC | GET | pass | 402 | 355 ms | — |
| 2026-10-01 10:30 UTC | GET | pass | 402 | 121 ms | — |
| 2026-09-25 10:31 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 130 ms | — |
| 2026-09-17 16:19 UTC | GET | pass | 402 | 159 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 118 ms | — |
| 2026-09-11 11:24 UTC | GET | pass | 402 | 195 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 189 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 208 ms | — |
| 2026-08-14 08:53 UTC | GET | fail | 402 | 108 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
1 of 1 paid attempts settled on-chain, and 1 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 matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count. The Stellar re-read checks payer, payee, amount and asset. A row reads as amount + payee when the re-read matched payer, payee, amount and asset and did not bind a one-time value. That tier holds rows from before 2026-09-04 and Stellar rows. They keep the settled label rather than being demoted (methodology). settled is the transfer vet402 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 re-read the transfer on-chain in that chain's pinned settlement asset, and the on-chain re-read matched the one-time value stored for that purchase, so the transaction is the one for this purchase. Stellar is not in this count.
L2 match- the response parsed as JSON and had the keys the listing marks as required. With an example that marks no key as required, a JSON object or array is enough.
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 | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-21 03:322026-10-21 03:32 UTC | settled (nonce-bound) | 200 | 0x61eb4fda…8d07 | Base | 1457 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | |||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 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/9e328d60-89a1-49db-b519-5f41bc57ef19)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.