hyperliquid-accounts.use.x402atlas.com/fees
1.Catalog declaration
| Resource URL | https://hyperliquid-accounts.use.x402atlas.com/fees |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xe79aa9d55170f7e1ac420266ec93a6c28c436de8 |
| Declared price (base units) | 10000 |
| Catalog status | active |
| First seen / last seen | 2026-08-16 01:06 UTC / 2026-10-20 01:01 UTC |
| Catalog-reported calls / payers (30d) | 7 / 5 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-19 16:40 UTC | GET | pass | 402 | 59 ms | — |
| 2026-10-18 04:40 UTC | GET | pass | 402 | 583 ms | — |
| 2026-10-16 21:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-10-15 12:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-10-14 03:40 UTC | GET | pass | 402 | 223 ms | — |
| 2026-09-30 10:30 UTC | GET | pass | 402 | 38 ms | — |
| 2026-09-25 10:30 UTC | GET | pass | 402 | 81 ms | — |
| 2026-09-20 11:24 UTC | GET | pass | 402 | 46 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 120 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 76 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 59 ms | — |
| 2026-09-06 11:24 UTC | GET | pass | 402 | 57 ms | — |
| 2026-09-01 23:14 UTC | GET | pass | 402 | 173 ms | — |
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 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 |
|---|---|---|---|---|
| 10-16 12:022026-10-16 12:02 UTC | settled (nonce-bound) | 200 | 0x7572bd17…9281 | 1516 ms |
| 10000 units (≈ $0.01 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/2b1372d5-7331-4601-9f9a-7bafe23a6274)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.