api.x402node.dev/forex/rate/jpy/usd/jpy-usd
1.Catalog declaration
| Resource URL | https://api.x402node.dev/forex/rate/jpy/usd/jpy-usd |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0x4466d4a84b7c49a6a094ec6eef4a0712d6dd125e |
| Declared price (base units) | 4000 |
| Catalog status | active |
| First seen / last seen | 2026-08-17 01:06 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 7 / 7 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 13:40 UTC | GET | pass | 402 | 117 ms | — |
| 2026-10-17 16:40 UTC | GET | pass | 402 | 65 ms | — |
| 2026-10-16 12:40 UTC | GET | pass | 402 | 93 ms | — |
| 2026-10-14 21:40 UTC | GET | pass | 402 | 118 ms | — |
| 2026-10-13 15:40 UTC | GET | pass | 402 | 210 ms | — |
| 2026-10-12 12:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-10-11 12:40 UTC | GET | pass | 402 | 279 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 63 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 182 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 147 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 126 ms | — |
| 2026-10-06 04:41 UTC | GET | pass | 402 | 72 ms | — |
| 2026-10-04 16:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-10-03 22:40 UTC | GET | pass | 402 | 261 ms | — |
| 2026-10-03 04:40 UTC | GET | pass | 402 | 2025 ms | — |
| 2026-10-02 13:40 UTC | GET | pass | 402 | 221 ms | — |
| 2026-10-01 13:40 UTC | GET | pass | 402 | 173 ms | — |
| 2026-09-30 16:40 UTC | GET | pass | 402 | 84 ms | — |
| 2026-09-29 22:40 UTC | GET | pass | 402 | 422 ms | — |
| 2026-09-29 04:40 UTC | GET | pass | 402 | 122 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 477 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 452 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-26 13:40 UTC | GET | pass | 402 | 467 ms | — |
| 2026-09-25 10:30 UTC | GET | pass | 402 | 78 ms | — |
| 2026-09-20 11:24 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 66 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 62 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 142 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 no_declaration- the listing declares no output schema to check the response against.
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 |
|---|---|---|---|---|
| 10-10 20:302026-10-10 20:30 UTC | settled (nonce-bound) | 200 | 0x9a35fadc…9783 | 1646 ms |
| 4000 units (≈ $0.004 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 10-02 18:002026-10-02 18:00 UTC | settled (nonce-bound) | 200 | 0xe77f62fe…6e2c | 1489 ms |
| 4000 units (≈ $0.004 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-26 06:002026-09-26 06:00 UTC | settled (nonce-bound) | 200 | 0x7859505f…5224 | 1219 ms |
| 4000 units (≈ $0.004 USDC) · L2 no_declarationWhose 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/aeeaaa67-1ea8-4fdd-aa55-41557f76494f)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.