Connecting exchanges

Bots trade in your own account on the venue you connect. BotRadix stores the connection details encrypted and uses them only to place, manage and close the bot's orders. Connections are managed in Settings on botradix.com.

Supported venues#

BotRadix DEX#

1. Open the DEX at app.botradix.com with your wallet and go to the API view.
2. Create a key. One wallet signature creates it and authorizes it for bots ("Automated execution" and "Enable for bots").
3. Copy the key, which is shown only once, and paste it in Settings → BotRadix DEX on botradix.com.

Bots on the DEX have network gas included and a per-order minimum equal to the market minimum plus a 0.5% buffer (with an 18 USDC minimum, 18.09 USDC; the screen may round it to 18.10). Disconnecting the key stops the bots; open positions stay on your DEX account. See Signatures and trading sessions and API overview and authentication.

Hyperliquid#

1. In Hyperliquid, create a dedicated Agent Wallet (also called an API wallet) for BotRadix.
2. In Settings → Hyperliquid, enter your main account address and the agent's private key.

Use an agent wallet created only for BotRadix, never your main wallet's private key. If you enter the agent's own address, BotRadix resolves the owner account automatically. BotRadix charges no fee on Hyperliquid; only Hyperliquid's own fees apply.

Uniswap (Base)#

1. Link your EVM wallet in Settings with a free signature (no transaction).
2. When you start a bot, approve the on-chain authorizations it asks for: a token allowance and per-market limits per trade and per day, maximum slippage and an expiry.

These authorizations are on-chain and revocable at any time from your wallet. Uniswap trading is spot only (1x): no leverage, no funding and no liquidation.

Extra protections on every bot swap, enforced by the contracts:

• Second signature. Each swap also needs the signature of a BotRadix co-signing service, kept separately from the key that sends it, so a single stolen executor key cannot trade (co-signing and its co-signers are configuration verifiable on chain). Without an available co-signer, Uniswap bots (including their stop-losses) wait until one returns.
• Price safety band. With the v2.2 reference configuration, a swap is rejected if the pool price is more than 10% away from the pool's 30-minute average price (3% when the backup co-signer signs); the code caps the band at 25%. Your maximum slippage is applied separately as a minimum amount received, so stop-losses can still sell in falling markets; no band guarantees stop-loss execution.
• Rate limits. With the v2.2 reference configuration, at most 240 swaps per hour per wallet and market (the code allows up to 3,600), and at least 20 seconds between a buy and a sell on the same market.
• Best pool. Each swap uses the pool that gives you the most after its fee, not the one with the most liquidity.

How your credentials are protected#

• Secrets (API keys and agent private keys) are encrypted at rest and decrypted only in memory at the moment they are used.
• They are never shown again in full: the interface displays a masked version (first and last characters).
• A connection cannot be changed or removed while bots or positions depend on it, to avoid leaving positions unmanaged.
• Account passwords are stored as one-way hashes, and two-factor secrets are encrypted.

Permissions to grant#

Grant only what trading requires:

• Trading and read access: yes.
• Withdrawals: no, whenever the venue allows you to disable them.
• Do not trade manually on the same markets the bots manage; manual changes can make the bot's records diverge from your real positions.