Perp dexs (HIP-3 builder-deployed)

Every builder-deployed perpetuals dex on Hyperliquid (HIP-3): dex name, full name, deployer, oracle updater and fee recipient, how many markets it lists (active vs delisted, so a wound-down dex reads as one), how many assets carry a streaming open-interest cap and the cap total, plus the current perp-deploy auction (start, end, start/current/end gas). Send POST /api/perp-dexs with no input and pay $0.002 per call over x402 or MPP (there is no free tier). It returns a JSON object with source, count, dexs, deployAuction and fetchedAt.

The native dex is not a row; use perp-markets for it. Keyless public data.

Category: Crypto & onchain data · Tags: crypto derivatives perpetuals hip-3 hyperliquid

TRY IN PLAYGROUND →

Parameters

Perp dexs (HIP-3 builder-deployed) takes no parameters.

Example request

curl -i -X POST https://agent402.tools/api/perp-dexs \
  -H "Content-Type: application/json" \
  -d '{}'

Without payment this returns HTTP 402 Payment Required with the exact price for perp-dexs; any x402 v2 or MPP client pays it and retries.

Example response

{
  "source": "hyperliquid",
  "count": 1,
  "dexs": [
    {
      "dex": "xyz",
      "fullName": "XYZ",
      "deployer": "0x88806a71d74ad0a510b350545c9ae490912f0888",
      "oracleUpdater": null,
      "feeRecipient": "0x83ffcfb1f2ad843c474b2e28df86c721cb869d3a",
      "subDeployers": 11,
      "assetsWithOiCap": 122,
      "totalStreamingOiCapUsd": 15820000000,
      "fundingMultipliers": 122,
      "markets": 123,
      "activeMarkets": 108,
      "delistedMarkets": 15
    }
  ],
  "deployAuction": {
    "startTime": "2026-09-18T01:00:00.000Z",
    "endTime": "2026-09-19T08:00:00.000Z",
    "durationSeconds": 111600,
    "startGas": 500,
    "currentGas": null,
    "endGas": 500,
    "active": false
  },
  "fetchedAt": "2026-09-18T12:00:00.000Z"
}

From an MCP client

catalog.call {
  "slug": "perp-dexs",
  "params": {}
}

The hosted connector at https://agent402.tools/mcp needs a payment for perp-dexs; the stdio package pays it from a wallet or from AGENT402_CREDITS_KEY. Local install: npx -y agent402-mcp.

Errors and behavior

• There is no input to get wrong: any request to /api/perp-dexs runs the tool.
• A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement is cancelled when the tool fails. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
• Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier. A prepaid card-credits key issued earlier (Authorization: Bearer a402_...) also pays it.
• A GET or HEAD to /api/perp-dexs returns the same 402 quote, so the price can be read without a body.
• An Idempotency-Key header makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).

Paid call (JavaScript agent)

import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";

const client = new x402Client();
client.setSpendControls?.(false); // keep your own spending ceiling in code
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);

const res = await payFetch("https://agent402.tools/api/perp-dexs", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({}),
});

Related tools