Connect a Hyperliquid API wallet#
Choose Mainnet or Testnet, name the connection and choose whether to include Spot. In a browser with a supported injected Ethereum wallet, the form can create and approve an API wallet. Desktop uses manual API-wallet credentials; WalletConnect is not configured.
Enter the main wallet address and the approved API wallet’s private key. If you paste an approved API wallet address instead, Schizo resolves its exchange-reported owner, verifies the key’s authorization for that owner, and shows the corrected main wallet in the review before saving. Do not enter a seed phrase or the main wallet private key. Optional subaccounts can be selected by address or an exact, unambiguous name. The review identifies the main wallet, signer, actual trading account and network before saving. Account queries use the trading account; the API wallet signs requests. There is no builder-fee approval step.
Changing networks clears credentials. Use a separate API wallet for each independent trading connection/process to avoid sharing nonce state. Spot uses available balances without borrowing; Portfolio Margin and unrecognized modes are blocked for Spot. Disabling Spot hides its market choices without selling assets or changing the exchange account mode. Hyperliquid Journal imports are not included in this integration.
Public-feed and mocked-transport tests do not establish every funded action. Follow Hyperliquid’s API-wallet guidance and verify private balances and existing orders for your selected account.
Use the exchange selector as your starting point#
The terminal includes account forms and transports for multiple exchanges. Look for the exact provider and product in Add Account, then enter the fields that form requests.
API-key providers commonly require a key and secret. Some also require an API passphrase. Wallet-based venues use different account or signing fields; an exchange login password is not a substitute for an API credential.
Connection and execution are separate checks#
A listed exchange, working public feed or saved key does not establish that all private actions work. Account products, regional restrictions, key types and signing methods can differ.
Bybit has been exercised as a live connection during this build’s development. Other included adapters need their own private-connectivity and order-execution checks for the account and hosting region in use.
Some writes for venues such as GRVT, Lighter, Aster and ApeX are restricted by the current compatibility policy. Do not change credentials or approve unrelated permissions to bypass a terminal restriction.
Connect Lighter#
Choose Mainnet or Testnet and either browser-wallet setup or Manual API key. Browser setup uses MetaMask, Rabby or another injected Ethereum wallet to approve a dedicated API key for an owned Lighter account. Desktop users can enter manual API credentials or perform wallet setup in their browser.
For manual setup, enter the numeric Account index, the separate API key index, and the Lighter API private key. Schizo derives the public key locally and verifies it against the registered key for that exact account and slot. Your main wallet private key is never requested. API credentials remain encrypted on this device.
Wallet setup uses an unused API key slot and keeps a prepared key available for retry if approval is declined or confirmation is interrupted. Revoke unused API keys in Lighter. Connection setup has no builder-fee approval or manual WebSocket switch. Trading uses inspected signed HTTP requests; streams recover automatically.
The integration targets perpetual futures. Supported signing paths include Market/Limit orders, protective orders, native groups, cancellation and leverage/margin-mode changes. Availability still depends on account and market rules. Fill-or-Kill, trailing stops and arbitrary account operations are unavailable. Public data and local signing tests do not establish funded execution for your account; verify the account and exchange responses after connecting. Open Lighter API keys ↗.
Use current provider instructions#
Follow your exchange’s own API-management guidance for creating credentials, permissions and product eligibility. The terminal’s general connection guide covers the common workflow; the provider controls its key settings and trading rules.