x402.ottoai.services/hyperliquid-market
Withdrawn from the catalog. This route is absent from a complete fetch of the public discovery catalog, so it is left out of the public L0 fail count.
1.Catalog declaration
| Resource URL | https://x402.ottoai.services/hyperliquid-market |
| Source | cdp_bazaar |
| Declared method | GET |
| Catalog network | eip155:8453 |
| Receiving address | 0x5bb4b0c766e0d5d791d9403fc275c22064709f68 |
| Declared price (base units) | 1000 |
| Catalog status | delisted (since 2026-10-26 13:05 UTC) |
| First seen / last seen | 2026-08-14 08:39 UTC / 2026-10-23 01:01 UTC |
| Catalog-reported calls / payers (30d) | 63 / 42 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-10-26 06:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-10-24 13:40 UTC | GET | fail | — | 10006 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-10-22 13:40 UTC | GET | fail | — | 10001 ms | timeoutNo response headers arrived within 10 seconds. |
| 2026-10-20 22:40 UTC | GET | pass | 402 | 437 ms | — |
| 2026-10-19 13:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-10-17 22:40 UTC | GET | pass | 402 | 537 ms | — |
| 2026-10-16 15:40 UTC | GET | pass | 402 | 772 ms | — |
| 2026-10-15 03:40 UTC | GET | pass | 402 | 401 ms | — |
| 2026-10-13 21:40 UTC | GET | pass | 402 | 343 ms | — |
| 2026-10-12 15:40 UTC | GET | pass | 402 | 323 ms | — |
| 2026-10-11 15:40 UTC | GET | pass | 402 | 346 ms | — |
| 2026-10-10 12:40 UTC | GET | pass | 402 | 209 ms | — |
| 2026-10-09 12:40 UTC | GET | pass | 402 | 412 ms | — |
| 2026-10-08 04:40 UTC | GET | pass | 402 | 677 ms | — |
| 2026-10-07 04:40 UTC | GET | pass | 402 | 415 ms | — |
| 2026-10-06 13:40 UTC | GET | pass | 402 | 548 ms | — |
| 2026-09-30 10:31 UTC | GET | pass | 402 | 292 ms | — |
| 2026-09-25 10:30 UTC | GET | pass | 402 | 246 ms | — |
| 2026-09-21 11:24 UTC | GET | pass | 402 | 315 ms | — |
| 2026-09-17 12:35 UTC | GET | pass | 402 | 113 ms | — |
| 2026-09-14 11:24 UTC | GET | pass | 402 | 235 ms | — |
| 2026-09-10 11:24 UTC | GET | pass | 402 | 262 ms | — |
| 2026-09-07 11:24 UTC | GET | pass | 402 | 404 ms | — |
| 2026-09-02 11:24 UTC | GET | pass | 402 | 213 ms | — |
| 2026-08-14 08:52 UTC | GET | fail | 402 | 126 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
3 of 3 paid attempts settled on-chain, and 3 of those also returned a deliverable 2xx response (delivered: other than 202 Accepted with a non-empty body). 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 a 2xx other than 202 with a non-empty body. 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 “attribution under review”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | On-chain tx | Payment chain | Latency |
|---|---|---|---|---|---|
| 10-18 15:312026-10-18 15:31 UTC | settled (nonce-bound) | 200 | 0x3ddebcbb…5513 | Base | 3526 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | |||||
| 10-12 14:322026-10-12 14:32 UTC | settled (nonce-bound) | 200 | 0xbca84e2e…ac20 | Base | 2739 ms |
| 1000 units (≈ $0.001 USDC) · L2 matchWhose side: no failure (delivered) | |||||
| 10-06 09:322026-10-06 09:32 UTC | settled (nonce-bound) | 200 | 0x50379f87…b072 | Base | 3774 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 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/acc4ff89-6be7-4875-b625-fc5451ded10c)4.Catalog listing events
| Detected on | Event | Before | After |
|---|---|---|---|
| 2026-10-26 | 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
A dispute does not start a purchase. The signed dispute route runs one fresh L0 check, an unpaid request.
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. This listing is not active in the catalog, so a dispute filed on the record form does not put it on the re-probe list. The record stays on this page. The scheduled L0 run is at 10:30 UTC. This listing is not on that run. Send the dispute to support@vet402.com. Published corrections are listed at /corrections. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference). That route runs one fresh L0 check under the normal publication gate. A later purchase comes from the regular schedule.