What You Need Before Your First Bot

Your first bot is easier to build when the account prerequisites are already clear. SteadyEdge separates account readiness, exchange readiness, strategy configuration, and historical validation.

What this is

This article is a pre-flight checklist before creating or launching a bot.

When to use it

Use this article if:

- you are about to create your first bot

- the editor blocks a required field

- you are not sure whether the issue is account, exchange, balance, or strategy related

Before you start

You should already have a SteadyEdge account and access to the dashboard.

Step by step

Step 1: Confirm account readiness

Before the first real workflow, confirm:

- your email is verified

- you understand your current plan limits

- you have enough daily backtest quota

- your available balance is not 0 if you plan to launch live

Step 2: Prepare the exchange account

You need at least one validated exchange account for live bots.

SteadyEdge currently supports Bybit and Binance connections in the account API tab. If you still need an exchange account, use SteadyEdge partner links: Bybit or Binance .

Step 3: Decide what the bot should trade

Before opening the editor, decide:

- exchange and market type

- symbol or all-coins mode

- long or short side

- sizing mode and leverage

- entry filter idea

- exit and risk rules

Spot behavior is long-only. Short behavior belongs to futures or margin-style contexts where supported.

Step 4: Plan the validation step

SteadyEdge requires a successful backtest before a bot can launch live. Treat the first setup as:

- create or clone a bot

- run a backtest

- review result and warnings

- launch only after validation passes

Step 5: Know what can block launch

Common blockers are:

- unverified email

- no validated exchange account

- zero or insufficient available balance

- config changed after the last passing backtest

- backtest failed or still pending

What you should see

When the checklist is complete, the editor can save the bot, the backtest flow can run, and the dashboard can show the bot with a clear next action.

Common mistakes

- creating API keys in the wrong exchange environment

- starting with live launch before the first backtest

- confusing bonus balance with available balance

- treating a failed account validation as a bot-editor problem

Related articles

- Connect Exchange Account

- Run Backtest

- Why Backtest Is Required Before Launch