> For the complete documentation index, see [llms.txt](https://docs.architect.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.architect.co/user-guide/architect-platform/home-page/orders-trades-and-algos.md). # Orders, trades and algos ## Orders The Orders section shows a recent history of orders sent. This includes the core order information as well as the status of the order (Fill, Out, Canceled, etc.) and any messages associated with the order (e.g. a reject reason). The Cancel All button will cancel all open orders, and each order can also be canceled from this page. ## Fills The Fills section shows a history of completed trades in your account. ## Algos The Algos section shows a brief summary of algorithmic orders, with further details available on the [Algos](/user-guide/architect-platform/algos.md) page. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.architect.co/user-guide/architect-platform/home-page/orders-trades-and-algos.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.