> For the complete documentation index, see [llms.txt](https://support.backpack.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.backpack.exchange/exchange/trading/order-types/market-orders.md).
# Market Orders
A **Market Order** is an instruction to buy or sell immediately at the best available price in the order book.
### **When to Use？**
* When you want your order to be executed instantly.
* Suitable for entering or exiting a position quickly, regardless of slight price changes.
### **Key Points**
* Execution is guaranteed, but the price may vary slightly due to market liquidity (slippage).
* Best for urgent trades, not for precise price control.
### How to Avoid Slippage Risk When Using Market Orders？
Open [**Backpack Exchange**](https://backpack.exchange/) and log in before following the steps below.
> New to Backpack? [Create an account](/exchange/exchange-account/create-a-new-account/how-to-create-an-account-on-the-web.md) to get started.
* On the **Spot** or **Futures** trading page, select the token you wish to trade.
* After confirming the trade direction, choose **Market Order**.
* Enter the order quantity.
* Click **Max Slippage Setting**, then enter the maximum slippage you are willing to allow.
* Confirm the order.
---
# 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://support.backpack.exchange/exchange/trading/order-types/market-orders.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.
