hyperliquid-setup

Configures Hyperliquid SDKs, network selection, and API wallet provisioning for trading desk environments.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/swcstudiospace/hypergrok-autonomous-desk --skill hyperliquid-setup-swcstudiospace
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hyperliquid-setup
Source: https://github.com/swcstudiospace/hypergrok-autonomous-desk/tree/main/skills/hyperliquid-setup
Command: npx skills add https://github.com/swcstudiospace/hypergrok-autonomous-desk --skill hyperliquid-setup-swcstudiospace

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires hyperliquid-python-sdk, eth-account, @nktkas/hyperliquid, viem.

What problem does it solve? Setting up a machine to interact with the Hyperliquid exchange involves installing SDKs, choosing between testnet and mainnet, verifying connectivity, and securely provisioning a trade-only API wallet. This Skill walks through each step so the desk environment is correctly configured and signing keys are handled safely. ## Core Features & Use Cases - SDK Installation: Installs the Python hyperliquid-python-sdk (3.9+) or the optional TypeScript @nktkas/hyperliquid client, plus curl and jq for read-only calls. - Network & Connectivity Verification: Checks both mainnet and testnet REST endpoints with a no-key allMids call and records the result. - Secure API Wallet Provisioning: Guides the user through creating a trade-only API wallet in the Hyperliquid app and loading its key via environment variable, secrets-manager command, or a mode-600 file, never in chat or workspace files. - Readiness Check: Runs a read-only verification that the API wallet is approved for the account before the first trade is sent. - Use Case: When moving a trading desk from research to testnet, use this Skill to install dependencies, confirm connectivity, provision the API wallet through the secret store, and run the readiness check. ## Quick Start Set up this computer for Hyperliquid testnet trading, install the SDK, verify connectivity, and walk me through provisioning an API wallet.

Frequently Asked Questions about hyperliquid-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up the Hyperliquid Python SDK for trading?▼

Install hyperliquid-python-sdk version 0.24 or higher with pip using the --user flag, then verify the install by importing hyperliquid and eth_account. Python 3.9 is required and 3.11 or later is preferred.

How do I create a Hyperliquid API wallet for automated trading?▼

Open the Hyperliquid app for your chosen network, connect your main wallet, and generate a new API wallet on the API page with a name and validity period. The app shows the private key once; store it through a secure secret store, never in chat or workspace files.

What is the difference between Hyperliquid testnet and mainnet endpoints?▼

Mainnet uses api.hyperliquid.xyz while testnet uses api.hyperliquid-testnet.xyz for both REST and WebSocket. Keys are network-specific because signatures encode the network, and testnet is the default unless HYPERLIQUID_NETWORK=mainnet is set deliberately.

Can a Hyperliquid API wallet withdraw funds from my account?▼

No, an API wallet cannot withdraw to Arbitrum, send USDC to other wallets, or approve other agents; those actions require the main wallet's signature. It can only place, modify and cancel orders and change leverage and margin.

Why does my Hyperliquid readiness check fail before the first trade?▼

Common causes include using the API wallet's address as the account address instead of the main wallet's address, signing with a key for the wrong network, or the agent not being approved yet. The readiness check reports which line disagrees so you can stop and fix it.

How do I rotate or revoke a Hyperliquid API wallet key?▼

Revoke the API wallet on the app's API page, which immediately stops all sends from the desk. To rotate, create a new API wallet, replace the secret in the secret card, secrets manager, or mode-600 file, then rerun the readiness check and journal the time.