> For the complete documentation index, see [llms.txt](https://lynx-finance.gitbook.io/lynx-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lynx-finance.gitbook.io/lynx-finance/welcome-to-lynx/core-design/trigger-bots.md). # Trigger Bots Every operation on Lynx - from opening a trade to liquidating a position - utilizes an ecosystem of trigger bots to complete the task. These bots are responsible for providing an updated and reliable price to be used when processing the operation. Most operations are done in two phases: first, a user registers their request (via an [Intent-Based Order System](/lynx-finance/welcome-to-lynx/cross-chain-perpetuals/intent-based-order-system.md)); then, a bot triggers the request. Trigger bots therefore constantly monitor the state of the platform, looking for requests that can be triggered. The use of these trigger bots offers two main benefits: 1. **Prevent Oracle Front-Running:** Prices are pulled on-chain and used in one single transaction, preventing traders from making opportunistic trades based on upcoming price updates 2. **Provide Up-to-Date Pricing:** Prices are retrieved at the exact moment that they're needed, offering the freshest and most reliable prices at a fraction of the cost of traditional price feeds --- # 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://lynx-finance.gitbook.io/lynx-finance/welcome-to-lynx/core-design/trigger-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.