> For the complete documentation index, see [llms.txt](https://docs.factor.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.factor.fi/factor-building-blocks/swap/concepts/market-orders.md). # Market Orders ## Overview A Market Order is an instruction to trade an asset at the best available price given current market conditions. Market Orders prioritizes settlement immediacy in favor of price predictability. This is because market conditions are constantly changing as buyers and sellers continuously adjusts their expectations based on the latest available data. As such, where immediate trades are required, the final settlement price of the trade can only be known after trade execution. Market Orders are exposed to slippage risks whereby the expected price and executed price for an order can differ depending on the market conditions. As there is always a certain amount of time between order placement and order execution, there is a possibility that market conditions might have changed during this short interval. By extension, slippage risks are also higher during periods of relative market volatility whereby asset prices tend to change more rapidly. The extent of slippage for a Market Order is dependent on the available liquidity for the particular swap pair. Commonly traded tokens will usually have greater market depth as market makers are able to profit from the constant trade volume being generated. On the other hand, there is a higher liquidity premium for exotic token swaps as there are less opportunities for market makers to earn a profit from arbitrageurs. Market Orders enable instant trade execution at the expense of price predictability. Traders can minimize their Market Order risks by utilizing [DEX Aggregators](/factor-building-blocks/swap/concepts/dex-aggregators.md) which have been integrated with the Swap Building Block. --- # 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://docs.factor.fi/factor-building-blocks/swap/concepts/market-orders.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.