> For the complete documentation index, see [llms.txt](https://docs.closed.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.closed.fun/telegram-bot-user-guide/limit-orders/limit-buy.md). # Limit Buy {% hint style="info" %} Limit orders get deleted automatically once executed or at the expiry time {% endhint %} 1. Start a regular [🟢 Buy](/telegram-bot-user-guide/editor.md) task by entering a token address or clicking 'buy' 2. Click Limit Orders
You will then be greeted by this screen
| Button | Action | Response | | ------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Buy | Should be green for a buy limit order | | | Sell | Should be red meaning not active | | | Expiry | Set the expiry time in minute e.g 60 for 1 hour | `When should your limit order expire? Set in hours (e.g., 0.5 = 30mins, 24 = 24 hours)` | | Gas Fee | Enter the amount in SOL you want to set your priority gas fee in, higher = quicker land | `Please enter the tip amount in SOL` | | Slippage | Set the buy slippage amount | `Please enter slippage percentage (e.g., 1 for 1%)` | | Price Limit |

Enter the percentage of the current price at which you want to create the order.


You cannot do this for a token that is not currently listed/trading on daos.fun

| | | MC Limit | Enter target mcap value. | | | Submit Order | Submit Limit Order | | | Close | Close the current Menu | | --- # 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.closed.fun/telegram-bot-user-guide/limit-orders/limit-buy.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.