Bots · Paper and LIVE workflows · Browser walkthrough

Bots: build, connect and monitor

The Bot Builder supports Paper and, where your account and a tested exchange connection allow it, LIVE workflows. Paper uses simulated activity; LIVE uses the selected exchange connection and can place real orders. Always check the mode shown in the Builder and review every setting before saving or activating.

Risk notice: Paper results are simulated and do not guarantee live results. LIVE trading can lose money. Never enable withdrawals on an exchange API key, and never share API credentials. Backtests use historical data and do not predict future performance.

In this section

Follow the steps for the task you need.

Member pages may ask you to sign in. Page contents and access can vary with your account.

Open the Bot dashboard and start a Bot draft

Use the dashboard to review your Bot workspace, then open Builder to choose a system. A draft is not active until you review and activate it.

Sign in, then open the member Workspace menu. On a phone, select Menu; on a wide screen, use the Workspace menu in the left sidebar.
Under Automate, select Dashboard to open the Bot control centre. If the page redirects you to Log in, enter your account details and continue.
Read the dashboard summaries and sections such as My bots, Open exposure, Activity, Performance and health. Check any data error or unavailable message rather than treating missing values as zero.
Choose Bot Builder from Workspace > Automate. The Builder shows three stages: Choose system, Configure and Review & activate.
On Choose system, select Signal bot, DCA, Grid or Market making, then select Continue with [system]. Each Bot uses one system.
Configure opens system-specific fields. Review Execution, the selected account/connection and the mode badge before completing the draft. Paper means simulated activity; LIVE means an exchange-connected workflow.
Select Save draft & review to save the configuration and advance. On Review & activate, check every displayed setting and the mode again. Activate bot starts the selected workflow; use it only when you intend to start that mode.
After activation, choose View bot dashboard or View activity. Return to the dashboard through Workspace > Automate > Dashboard.

Open Bot dashboard

Manage Bots and browse the Bot Library

Manage Bots is where you review saved Bot configurations and their available controls. Bot Library groups the available strategy and research tools.

From Workspace > Automate, select Manage Bots to see saved Bots and their displayed mode and status.
Open the Bot’s available details to review its configuration. Use Activate or Pause only when you intend to change its running state; confirm the mode before doing so.
Delete removes the selected configuration. If you choose Delete, read the confirmation carefully; Delete permanently cannot be treated as a pause action.
To inspect the library catalogue, open the Workspace menu and select Bot Library.
Open a library card to see its current contents. The library can include Strategies, Templates, Technical indicators, Candle patterns, Backtester, Paper accounts and Algorithm intelligence; a card marked Not enabled is unavailable to your account.
For a backtest, open the Backtester and set only the parameters you understand. Check the market, period, fees, slippage and execution assumptions shown before selecting Run backtest. Historical simulation is not a forecast or a guarantee of live performance.
Use the Workspace menu to return to Dashboard or Manage Bots.

Open Manage Bots

Build a Strategy Bot in Paper or LIVE mode

The Builder offers Signal bot, DCA, Grid and Market making. Each system displays its own configuration fields; follow the fields shown rather than assuming all systems work alike.

Open Workspace > Automate > Bot Builder, choose the system and select Continue with [system].
Give the Bot a recognisable name. Under Execution, choose Paper or LIVE if LIVE is enabled for your account. Paper uses the displayed Paper account; LIVE requires a tested LIVE connection. Confirm the exchange/account shown before proceeding.
For Signal bot, select the Pulse strategy, timeframe and Signal engine (V1 or V2); V2 sets the timeframe according to the screen. Choose Paper or LIVE, then set the leverage. Review shows the risk-at-stop and position policy used by this Signal Bot.
For DCA, Grid or Market making, enter the USDT market and select Long or Short when the field appears. Complete only the displayed system fields: DCA entry interval, maximum entries and allocation; Grid lower/upper price, ladder levels and allocation; Market making quote size, spread and refresh interval. Then complete leverage, stop-loss and take-profit fields within the ranges shown. This guide does not prescribe trading settings.
Select Save draft & review. Check system, execution mode, exchange/account, market and all rules on Review & activate. If anything is wrong, go back and correct it.
Optional: if the review screen offers Run backtest, check the selected system, market, historical period, fees and slippage first. Select Run backtest to produce a historical simulation. Review the result as historical evidence only, not a prediction.
To start the selected workflow, select Activate bot only after the review. The LIVE path may also require the separate live-execution switch. Confirm the resulting status, then use the dashboard and Activity page to monitor it.
Strategy Bot exchange workflows reference Binance, OKX, Bybit and Bitget. Availability can depend on the selected system, connection and account access; use the exchange options actually shown in your Builder.

Read the Bots product overview

Run a paper scan in the separate Arbitrage workspace

The on-chain Arbitrage workspace is separate from Strategy Bots and offers Solana and BSC route evaluation in Paper mode only. It does not sign a wallet transaction or submit a live order.

Open Workspace > Automate > Exchange Arbitrage. Confirm the page says Paper only; this workflow simulates observations and does not expose live order placement.
Choose the Solana or BSC tab. Enter the settlement mint/token and its decimals. On Solana, also enter the intermediate mint, its decimals and the input amount. On BSC, enter the input amount and complete both Router legs with venue, router address, token-in/token-out addresses and decimals.
Complete the displayed assumptions: minimum net profit, maximum slippage, maximum quote age, gas cost, priority fee and relay tip. Check the token addresses and decimal counts carefully; these are inputs for an evaluation, not a wallet-connection form.
Select Run paper scan. Review warnings and each route result’s status, quote age, gross amount, estimated slippage, costs, net amount and explanation. If no route appears, the required inputs may be incomplete or no route met the configured checks.
The page is explicitly marked Paper only and says no order is signed or submitted. Do not interpret an eligible paper result as a live execution or realised profit; the page has no activate control for live Arbitrage orders.

Read the Arbitrage Bots overview

Add and test an exchange connection for LIVE Bots

Paper workflows use an Edge Theory Paper account. LIVE Bot workflows require an exchange API connection; the connection form confirms that withdrawals are disabled.

Open Workspace > Automate > Exchange Connections. If the page is unavailable for your account, use the access message shown there; do not infer plan entitlements from an old guide.
On the exchange’s official website, create an API key with withdrawals disabled and only the permissions required for the intended Bot. Follow the exchange’s own security instructions.
In Edge Theory, open Workspace > Automate > Exchange Connections. Select the exchange, enter a connection name and account label, then enter the API key and secret. Enter an API passphrase when required for that exchange.
Tick the confirmation that withdrawals are disabled, then select Save LIVE API connection. Credentials are not shown again after saving.
In Saved accounts, find the connection and select Test connection. Continue only if the test succeeds and the connection status is displayed as connected/enabled.
Return to Bot Builder, select LIVE in the Mode field and choose the tested connection from the LIVE connection list. A connection alone does not activate a Bot; the separate live-execution control may still be required.
Never paste credentials into Help, chat or support. If a key may have been exposed, revoke it from the exchange immediately. Delete a saved connection only after checking which Bots depend on it.

Open Exchange Connections

Review Bot Activity and identify its execution mode

Activity reports recorded checks, orders, positions and issues. Verify whether each record is Paper or LIVE before interpreting it.

Open Workspace > Automate > Bot Activity.
Read the page heading and choose any displayed Bot or date filters to narrow the report.
For each row, inspect its timestamp, Bot name, event/status, market and execution mode where shown. Distinguish simulated Paper events from LIVE exchange events.
Open a row or its details control if available to read the recorded event and any error. Do not assume a missing row means a Bot is healthy or that no exchange-side event occurred.
If an event is failed, unresolved or unclear, note the non-sensitive message and Bot name, then check Bot Health. Do not share API secrets or recovery codes with support.
Use the Bot control centre link or Workspace menu to return to Dashboard.

Open Bot Activity

Read Bot Statistics without mixing Paper and LIVE results

Statistics summarise recorded Bot activity. Check the mode and period in the report before drawing conclusions; historical performance is not a forecast.

Open Workspace > Automate > Bot Statistics.
Read the page description, then select the Bot and time range using the available filters, if shown.
Check the execution mode for the selected records. Paper statistics are simulated; LIVE statistics refer to recorded exchange-connected activity only where the report labels them that way.
Review the displayed totals and any breakdowns. Keep open, unsettled or unresolved activity separate from completed records where the page does so.
If statistics are empty or show an error, treat them as unavailable. Do not fill gaps with estimates or infer future returns from historical results.
Use the Bot control centre link or Workspace menu to return to Dashboard.

Open Bot Statistics

Check Bot Health and respond to status messages

The health page reports registry and runtime status for configured Bots. A failed page load is not a healthy status.

Open Workspace > Automate > Bot Health.
Read Bots checked, Attention required and Healthy at the top of the page.
In Runtime health, inspect each Bot’s name, type, mode, status label, detail and last-run error.
Select Refresh health and wait for the request to finish. Read any displayed error rather than interpreting a failed refresh as a healthy result.
If a Bot shows recovery required, select Review activity to inspect the related event. Use the Bot’s own controls only after understanding the issue and confirming the mode; Pause stops a running workflow, while Activate starts one.
If the health request fails, or the page is empty unexpectedly, report that exact state to support. Do not treat missing data as confirmation that a Bot is healthy.

Open Bot Health

Use Strategy Designer and the specialist Bot pages

Strategy Designer has separate design and historical test controls; DCA, Grid and Bot family workspaces are available as separate destinations. Check each page’s mode and assumptions before using a control.

Open Workspace > Automate, then choose Strategy Designer, DCA Bot, Grid Bot or Bot Library, depending on the task.
In Strategy Designer, select New strategy. Enter Strategy name, Symbols, Timeframe, Risk budget per trade % and a description. Choose the entry rule in the visual designer: SMA cross, Range break or Candle direction; set its direction/conditions and the structural ATR stop and target controls shown.
Review the entry, risk and exit definition, then select Save immutable version. Each save creates a fixed version. To edit later, change the definition and save a new version rather than expecting the old version to change.
In My library, select the saved strategy/version. In Test strategy, choose a Market from the symbols in that version. Select Quick check, Run full backtest, Optimise parameters or Walk-forward test. These controls use the page’s displayed Bybit market-data and historical-test assumptions; wait for the result before starting another test.
Read the result summary and the available Overview, Trades or Equity view. Check the trade list, net PnL, win rate, realised R and drawdown alongside the tested market and sample. A backtest is a historical simulation, not a forecast or guarantee, and does not activate a Bot.
In DCA Bot, Grid Bot or a Bot family page, read the page’s mode, input labels and confirmation copy. Use Save only after reviewing every field. Check the resulting Bot in Manage Bots and Bot Health.
Return through the Workspace menu. If a control’s effect or execution mode is not clear on screen, do not submit it; ask support with the page name and non-sensitive details.

Open Strategy Designer

All Help topics Contact support