> For the complete documentation index, see [llms.txt](https://arbital-1.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://arbital-1.gitbook.io/docs/automated-strategies/execution-modes.md). # Execution Modes Arbital bots offer three execution modes, depending on how aggressive you want to be. ## Aggressive * Fastest order refresh * Orders closer to top of the book/mid price * Higher volume generation in a short period of time Aggressive mode will allow you to hit the target volume fastest, but is more prone to slippage and faster inventory accumulation during volatile conditions. ## Normal (Default) * Balanced refresh * Moderate spreads * Stable inventory behavior Normal mode offers the best balance between volume generation and execution quality, reducing slippage while maintaining consistent fills. ## Passive * Slower refresh * Wider spreads * Lower fees, fewer fills Passive mode prioritizes execution quality and fee efficiency over speed, resulting in lower volume but reduced slippage and inventory churn. --- # 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://arbital-1.gitbook.io/docs/automated-strategies/execution-modes.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.