Add to Dashboard

After generating your exchange API key, add it to the Aegis dashboard as an execution wallet. An execution wallet is the combination of an exchange account, a bot type, the owner/exchange account address, and the API credentials used for futures hedging.

Add Wallet Form

Open the dashboard and navigate to Futures Wallets (or the execution wallet management section).
Click Add Wallet (or the equivalent button in the current dashboard build).

Fill in the fields that are common to every venue:

Field	Description
Exchange	Select the exchange: Binance Futures or HyperLiquid. (BingX — Coming soon.)
Bot type	Select the bot type: Bastion, Vanguard, or Orbit. This field is mandatory and cannot be changed after the execution wallet is saved.
Name / Label	A user-defined identifier for this execution wallet (for example, `bastion-eth-usdc`).
Wallet address	The owner/exchange account public address associated with these API credentials. For HyperLiquid: your main account address (not the agent wallet address). This is distinct from your LP wallet address used for on-chain scanning — see Wallet-Bot Binding.

Fill in the credential fields — these differ by venue:

Binance Futures:

Field	Description
API key	The exchange-issued Binance Futures API key string.
API secret	The exchange-issued Binance Futures API secret string.

HyperLiquid (no manual “API key” field is shown):

Field	Description
API Key Secret	The agent wallet private key (64 hex characters) generated when you created the HyperLiquid agent wallet. This is the only secret HyperLiquid needs.
Agent wallet address	Not entered by you. After you save, Aegis derives the agent wallet address server-side from the API Key Secret and displays it back on the confirmation screen.

Confirm and save.
- Binance: the API key and API secret are encrypted together with AES-256-GCM at rest immediately upon saving.
- HyperLiquid: the API Key Secret (agent private key) is encrypted with AES-256-GCM at rest immediately upon saving, and the derived agent wallet address is shown back to you once.
In both cases the credential material is never displayed back in the dashboard after this point. If you need to update a key, you must remove the execution wallet and add a new one.

Bot Type Is Fixed at Creation

The Bot type field determines which bot strategy will run against this execution wallet. It is set at creation time and is immutable — it cannot be changed via the dashboard once the execution wallet is saved.

Available bot types:

Bastion — downside and upside short protection strategy.
Vanguard — breakout long on upside move strategy.
Orbit — mean-reversion long/short on range edges strategy.

Ensure you select the correct bot type for the strategy you intend to run.

Multi-Bot Usage

To run multiple bot strategies (for example, both Bastion and Vanguard on the same exchange), you must create separate execution wallets — one per bot type. Each execution wallet is independent and maps to one bot instance.

Example:

bastion-eth-usdc — Bastion bot type, Binance Futures.
vanguard-eth-usdc — Vanguard bot type, Binance Futures.

Both execution wallets can use the same exchange account but must have distinct credentials (a distinct API key/secret pair on Binance, a distinct agent wallet API Key Secret on HyperLiquid).

For the one-wallet-per-symbol constraint, see Wallets — Wallet-Bot Binding.

Permission Validation

Beta / Pending UX — Automatic permission validation (checking whether the provided credentials have the correct permissions) and excessive-permissions warnings on the Add Wallet form are not yet live. Before saving, manually verify your API key permissions (Binance) or agent wallet permissions (HyperLiquid) match the requirements in API Keys Overview.