> For the complete documentation index, see [llms.txt](https://docs.pages.koto.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pages.koto.trade/product/bots.md). # Bot Bot gives eligible users a controlled way to automate trading activity. It is designed for users who want Koto to help run repeatable trading strategies while keeping account access, risk limits, and bot status visible. ## Business Purpose Koto Bot helps users participate in trading activity without manually placing every order. It is also designed to support campaigns or points programs where automated activity may be eligible under specific rules. The product is not meant to be an unmanaged key vault. Users connect trade-only access, choose bot settings, and retain controls to pause, resume, inspect, or remove automation where available. ## Description The Bot experience has two user-facing parts: * Account and API-key setup: users connect a trading account or create trade-only access that can place trades but cannot withdraw funds. * Managed trading bots: eligible users create bots, select an account, choose a strategy and pair, set risk controls, and monitor activity over time. Bot availability can depend on account eligibility, connected accounts, supported exchanges, enabled strategies, capacity, cooldowns, and campaign or product availability. ## How It Works 1. The user signs in and prepares a trading account. 2. The user connects an eligible exchange or account using trade-only access. 3. Koto confirms that the access is intended for trading and not withdrawals. 4. The user creates a bot when capacity and eligibility allow it. 5. The user selects the account, market pair, strategy, and risk settings. 6. The user reviews the setup before the bot goes live. 7. Once active, the bot trades according to the selected strategy and the user's configured limits. 8. The user monitors bot status, volume, PnL, risk, and account usage. 9. The user can pause, resume, remove, or create additional bots where allowed. ## What It Supports * Trade-only account or API-key setup. * Withdrawal-off expectations for connected access. * Connecting eligible accounts and viewing linked account status. * Managed bot creation for eligible users. * Strategy selection where available, including volume-style, grid-style, and DCA-style strategies. * Pair and account selection for each bot. * Risk controls such as max loss, stop settings, account availability, and strategy limits where supported. * Bot lifecycle controls such as create, pause, resume, inspect, and remove. * Bot status, active bot count, volume, PnL, and risk monitoring. * Capacity and cooldown messaging when the user cannot create a new bot immediately. * Competition or points participation only when the relevant program rules allow bot activity to count. ## Bot Details ### Account And Access Setup Before creating a bot, users connect a trading account or create trade-only access. Trade-only access is meant to let the bot place trades, not withdraw funds. Users should only connect access that is intended for automation and should review permissions before continuing. ### Managed Bot Setup When creating a managed bot, users choose the account the bot will trade with, the market pair, the strategy, and the risk settings. A review step should summarize the setup before the bot starts so the user can confirm the account, pair, strategy, and limits. ### Strategy Types * Volume-style bot: designed to generate trading activity on a selected pair while following the configured limits. * Grid-style bot: places a ladder of buy and sell orders across a selected price range where available. * DCA-style bot: builds a position in steps and uses configured exits or risk controls where available. Strategy availability can differ by user, account, exchange, pair, or product availability. ### Risk And Monitoring Users should be able to see whether a bot is running, paused, or unavailable. Monitoring can include total bot count, active bots, generated volume, PnL, account usage, and risk information. Risk settings such as max loss or stop settings help define when automation should stop or reduce exposure. ### Lifecycle Controls Users can create a bot when eligible, pause or resume it where supported, inspect bot details, and remove it when they no longer want it active. Capacity limits and cooldowns may prevent immediate creation of additional bots. Automation still carries trading risk. Trade-only access helps protect withdrawals, but it does not remove the risk of market losses. Users should review strategy settings, account balance, and risk limits before starting a bot. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.pages.koto.trade/product/bots.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.