> For the complete documentation index, see [llms.txt](https://stackerai.gitbook.io/stacker-ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stackerai.gitbook.io/stacker-ai/how-it-works/stacker-algorithm.md). # Stacker Algorithm In the rapidly evolving world of AI asset management, StackerAI stands at the forefront, pioneering an AI-driven approach that melds sophisticated algorithms, comprehensive data analysis, and strategic foresight. Our methodology is not just a process; it's a symphony of technological innovation and financial acumen. Our algorithm consists of a series of AI agents all trained in and tasked with a unique position to provide a comprehensive overview of live market and historical data. This information is processed through a unique data pipeline to provide comprehensive decision making, allowing us to minimize risk while maximizing reward. The incorporation of machine learning provides constant feedback and optimization. Each unique trade is analyzed for improvement opportunities which are automatically implemented into the trading strategy. --- # 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://stackerai.gitbook.io/stacker-ai/how-it-works/stacker-algorithm.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.