A Bybit AI Subaccount can separate an automated workflow from your main trading account, but separation is not the same as safety. The agent can still place bad trades, use excessive leverage, request transfers or expose credentials within the permissions and limits you authorize. This guide explains the current setup model and a least-privilege checklist for using AI or API tools.
What the Bybit AI Subaccount is
Bybit’s official AI Subaccount guide describes a dedicated subaccount that can be connected to an AI agent. The main account manages the connection and permissions. The documented controls include transfer requests, a daily transfer-in limit, a cap on funds held in the AI Subaccount, internal account transfers, leverage limits and futures take-profit/stop-loss limits.
This structure can limit the scope of an automation error if the permissions and caps are conservative. It does not verify an AI strategy, guarantee a stop price, prevent API misuse or protect funds that you deliberately make available to the agent.
AI Subaccount, standard subaccount and ordinary API key
| Option | Primary use | Key risk question |
|---|---|---|
| AI Subaccount | Connect an AI agent with subaccount-level permission controls | What actions and funding limits will the agent receive? |
| Standard subaccount | Separate strategies, teams or operational accounts | Which account and API permissions apply to each strategy? |
| Main-account API key | Programmatic access to allowed main-account functions | Could a compromised key affect more capital or products than necessary? |
Use the narrowest account type and permission set that can perform the required task. If a tool only needs market data, it should not receive trading or asset permissions. If it only needs to trade one small strategy, it should not control the full trading balance.
Before connecting any AI agent
- Verify the software and publisher. Use the official project site or repository, check update history, and avoid a link delivered through an unsolicited message.
- Understand where prompts and secrets go. A cloud agent may process commands, logs or credentials on third-party infrastructure.
- Read the requested permissions. “Connect” should never be treated as a harmless login step.
- Plan a kill switch. Know how to revoke the connection, disable the API key and close positions from the main account.
- Choose a loss budget. Set the subaccount cap from the amount you can afford to lose, not from the agent’s claimed performance.
Do not connect an agent merely because its interface mentions Bybit or because a public prompt promises automated profit. An integration can be technically compatible and still be insecure, unreliable or unsuitable for your jurisdiction.
Create the AI Subaccount from the official Bybit interface
According to Bybit’s current instructions, the app path begins from Settings → Subaccount → Create, after which the user selects AI Subaccount and completes security verification. The exact labels can change. Start from the official app or a verified Bybit bookmark and follow the path shown in your account.
- Give the subaccount a name that identifies one strategy and one environment.
- Do not reuse production credentials for development or testing.
- Complete the connection from a clean, trusted device.
- Record the creation date, purpose, owner, agent and approved limits.
- Take a screenshot of the original permission configuration for later review.
Understand the connection and credential lifetime
Bybit’s guide describes a Copy & Connect flow and a manual public-key process for some cloud agents. It states that a generated API key expires in 90 days under that flow, while advanced settings such as longer validity, IP whitelisting, permission scope and rate limits are managed on the web platform. Verify the expiry displayed for your key rather than assuming every key follows the same rule.
- Never paste an API secret into a public issue, chat room, shared document or unverified prompt.
- Store secrets in the agent’s supported secret manager, not directly in source code.
- Treat screenshots and logs as sensitive if they can reveal keys, commands or account identifiers.
- Rotate or revoke credentials after an incident, team change or vendor change.
- Remove an expired or unused key instead of leaving it attached to the account.
Set permissions and limits from the main account
Bybit documents management from the main account’s Subaccount area. Review every control separately. “Enabled” usually means the agent can perform or request the action within the configured rules; it does not mean the action is always appropriate.
| Documented control | Purpose | Conservative review question |
|---|---|---|
| Request Transfer In | Allows the agent to request funds from the main account | Does this strategy need to request more funds at all? |
| Daily Transfer In Limit | Limits the USD amount transferred in within 24 hours | Is the limit below the maximum daily loss budget? |
| Cap Limit | Caps funds held by the AI Subaccount | Could I tolerate losing the full capped amount? |
| Request Transfer Out | Allows transfer back toward the main account under the documented flow | Can this be disabled until it is genuinely required? |
| Move from Trading / Funding | Controls internal movement between UTA and Funding | Which account does the strategy actually need? |
| Max Margin Leverage | Sets the maximum margin leverage available to the agent | Why is leverage required, and what liquidation risk follows? |
| Max Contract Leverage | Sets the maximum contract leverage | Can the strategy work with a materially lower maximum? |
| All Futures TP/SL | Limits take-profit/stop-loss parameters for futures positions | Do the limits prevent obviously unacceptable orders without blocking emergency exits? |
Bybit’s guide notes a default 5,000 USD cap at the time of its update, but a default is not a recommendation. Confirm the current value shown in your account and reduce it to a test-sized amount before authorizing the connection.
What fund isolation can and cannot do
A subaccount can separate balances and operational records, but “full segregation” is too strong a claim. Actual exposure depends on account architecture, transfer permissions, unified margin behavior, collateral, open positions and the main-account controls you authorize.
- It can help: limit the funds intentionally allocated to one automated workflow.
- It can help: separate logs, positions and credentials for different strategies.
- It cannot: make an unprofitable strategy profitable.
- It cannot: guarantee that leverage, stops or API actions behave as expected in fast markets.
- It cannot: protect the main account if you authorize broad transfers or expose main-account credentials elsewhere.
- It cannot: remove platform, custody, legal or market risk.
API least-privilege checklist
Bybit’s V5 API documentation covers market data, order, position, account and asset functions. Only enable the categories the implementation truly uses.
- Use read-only access for analytics, alerts and portfolio display.
- Separate trading keys from administrative or asset-management workflows.
- Use IP restrictions when the agent has stable, controlled outbound addresses.
- Set rate limits and application-level order-size limits.
- Do not allow withdrawal or transfer capabilities merely for convenience.
- Create separate keys for production, testing and each vendor.
- Monitor failed authentication, unexpected endpoints and unusual order frequency.
An IP whitelist is useful only if the infrastructure is controlled and the address will not be shared with untrusted workloads. A compromised server on the whitelisted IP can still misuse the key.
Test the automation before funding it
- Use testnet or a non-funded dry-run environment when the tool supports it.
- Verify symbol, side, order type, quantity, price, time-in-force and reduce-only behavior.
- Test rejected orders, timeouts, duplicate requests and reconnects.
- Confirm that retries cannot create duplicate positions.
- Test the emergency stop and credential revocation process.
- Fund the live subaccount with the smallest practical amount.
- Watch the first complete trade lifecycle in real time.
Automated systems fail in edge cases: stale data, partial fills, network timeouts, clock drift, rate limits, schema changes and a model that misunderstands an instruction. A successful backtest does not test those operational failures.
Leverage and stop-loss controls are not guarantees
A maximum-leverage setting is a ceiling, not a safe target. Keep it lower than the highest level a strategy could technically use. Take-profit and stop-loss controls can reduce certain risks, but execution can occur beyond a trigger during volatility or liquidity gaps. An agent can also create many individually small positions whose combined exposure is large.
- Set both per-order and total-position limits in the agent where possible.
- Limit the number of open positions and correlated symbols.
- Use reduce-only logic for closing orders and verify it in practice.
- Include fees, funding and slippage in risk calculations.
- Do not automatically transfer more money to rescue a losing strategy.
Review our Bybit futures guide for contract, margin, funding and liquidation mechanics. For broader AI trade confirmation and permission risks, see the Bybit AI Hub guide.
Continuous monitoring and incident response
- Review balances, open positions, orders, transfers, sessions and API keys daily during initial testing.
- Alert on unexpected symbols, leverage, order size, transfer requests and drawdown.
- Reconcile Bybit activity with the agent’s logs; preserve timestamps and request IDs.
- Pause after any unexplained action rather than allowing the agent to “fix” it automatically.
- Revoke the connection and keys before investigating a suspected compromise.
Keep a written incident sequence: stop new orders, cancel open orders where appropriate, close or hedge positions only after checking the risk, revoke credentials, preserve evidence, change exposed secrets and contact official support. Practice it before a real loss.
Pre-authorization checklist
- I verified the agent and understand where its data is processed.
- I can explain every enabled permission in one sentence.
- The daily transfer limit and cap are within my loss budget.
- The maximum leverage is conservative and necessary.
- Secrets are stored outside source code and shared documents.
- I tested duplicates, errors, stops and revocation.
- I have alerts and a person responsible for monitoring.
- I accept that AI output and API execution can be wrong.
Affiliate disclosure: ByDITT may receive compensation if you register through this link. Any code, campaign or fee benefit depends on the current account, region and terms. It does not validate an AI agent, guarantee performance, or protect against API, custody or trading losses.
Educational information only, not financial, security or software advice. Features and limits can change. The settings displayed in your own Bybit account and the current official documentation take precedence.
