api.x402node.dev/forex/rate/cny/hkd/cny-hkd
1.Catalog declaration
| Resource URL | https://api.x402node.dev/forex/rate/cny/hkd/cny-hkd |
| 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-25 01:58 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-15 15:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-10-14 12:40 UTC | GET | pass | 402 | 285 ms | — |
| 2026-10-12 21:40 UTC | GET | pass | 402 | 220 ms | — |
| 2026-10-11 21:40 UTC | GET | pass | 402 | 236 ms | — |
| 2026-10-10 21:40 UTC | GET | pass | 402 | 140 ms | — |
| 2026-10-09 21:40 UTC | GET | pass | 402 | 109 ms | — |
| 2026-10-08 16:40 UTC | GET | pass | 402 | 357 ms | — |
| 2026-10-07 13:40 UTC | GET | pass | 402 | 299 ms | — |
| 2026-10-06 16:40 UTC | GET | pass | 402 | 161 ms | — |
| 2026-10-05 04:40 UTC | GET | pass | 402 | 193 ms | — |
| 2026-10-04 13:40 UTC | GET | pass | 402 | 1604 ms | — |
| 2026-10-03 13:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-10-02 16:40 UTC | GET | pass | 402 | 2187 ms | — |
| 2026-10-01 22:40 UTC | GET | pass | 402 | 474 ms | — |
| 2026-10-01 04:40 UTC | GET | pass | 402 | 2275 ms | — |
| 2026-09-30 13:40 UTC | GET | pass | 402 | 339 ms | — |
| 2026-09-29 13:40 UTC | GET | pass | 402 | 97 ms | — |
| 2026-09-28 16:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-09-28 04:40 UTC | GET | pass | 402 | 347 ms | — |
| 2026-09-27 13:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-26 16:40 UTC | GET | pass | 402 | 172 ms | — |
| 2026-09-25 22:40 UTC | GET | pass | 402 | 329 ms | — |
| 2026-09-25 04:40 UTC | GET | pass | 402 | 73 ms | — |
| 2026-09-24 13:40 UTC | GET | pass | 402 | 122 ms | — |
| 2026-09-23 16:40 UTC | GET | pass | 402 | 289 ms | — |
| 2026-09-22 22:40 UTC | GET | pass | 402 | 182 ms | — |
| 2026-09-22 04:40 UTC | GET | pass | 402 | 146 ms | — |
| 2026-09-21 13:40 UTC | GET | pass | 402 | 94 ms | — |
| 2026-09-20 16:40 UTC | GET | pass | 402 | 142 ms | — |
| 2026-09-19 22:40 UTC | GET | pass | 402 | 104 ms | — |
3.L1 — real purchases
2 of 2 paid attempts settled on-chain, and 2 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 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 |
|---|---|---|---|---|
| 09-17 18:012026-09-17 18:01 UTC | settled (nonce-bound) | 200 | 0x0f9b80a4…afe8 | 1606 ms |
| 4000 units (≈ $0.004 USDC) · L2 no_declarationWhose side: no failure (delivered) | ||||
| 09-04 09:232026-09-04 09:23 UTC | settled (amount + payee) | 200 | 0x933cf474…58c2 | 1154 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 2/2 settled · 2 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/293f7086-e9f1-4ba6-b370-3a7668a6126e)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.