Page cover

Auto-Trade Bot Setup and Settings Guide

Initial configurations

When you first open the Mefai Autotrade page, your balance information will not be visible because an API key has not been added yet. First, click the "Edit" button in the API key section. Enter your API key and secret. Please note that you will only see your secret key once, even on Binance, so be sure to save it somewhere safe. After filling in the API key and secret, press the "Test Key" button. If the test result is successful, save your API by clicking the "Save" button.

Before activating the Autotrade button, check if you have any open positions. If you have open positions, Autotrade will not activate. Please ensure that you have closed all your trades first.

After activating Autotrade, you will see that the log screen, signal screen, and chart screen have appeared on your page.

Next, you only need to configure your settings in the section below and click "Save" once. After this, positions will begin to open and close according to the time and pair you have selected. If you wish to change your API keys, first deactivate Autotrade. Then, you can make the necessary changes in the API key section, test them, and click the "Save" button.

When Autotrade is activated, you will see a screen like this. At the top, you can view the log records in your selected language, showing what’s happening in Autotrade.

The TradingView chart for your selected pair and timeframe appears on the right side. Additionally, the latest MEFAI signal for that timeframe is displayed at the top of the screen.

If a new signal arrives during this time, the approval process begins. This process continues until the candle for that timeframe closes or one side gains a clear advantage. Once the outcome is determined, the trade is executed.

Make sure you read this document carefully to fully understand how this candle battle works. https://mefai.gitbook.io/mefai-docs/mefai-doctrine/sacred-doctrine For position management and information on others, please make sure to read the entire documentation.

Last updated