> For the complete documentation index, see [llms.txt](https://docs.proliquid.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.proliquid.xyz/order-types/market-orders.md).

# Market orders

Market order type in Proliquid trade form

<div align="left"><figure><img src="https://1571380119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwUo1o7rINODRyyILQE1%2Fuploads%2F69qyEd5hWfVmdJXmSQua%2Fimage.png?alt=media&amp;token=d2a73020-bc03-4458-8dae-ce45cd27e1a4" alt="Market order form with available margin, position, quantity, notional, reduce-only, and TP/SL controls."><figcaption><p>Market order form with available margin, position, quantity, notional, reduce-only, and TP/SL controls.</p></figcaption></figure></div>

Market orders are for fast execution on the selected market. Where the active exchange supports a slippage guard, it limits how far execution can move from the current price.

Use Market when speed matters more than maker-only execution. For price control or maker intent, use [Limit](/order-types/limit-orders.md), [Chase](/order-types/chase-orders.md), or [TWAP](/order-types/twap-orders.md).

## Inputs

<table><thead><tr><th width="163.125">Control</th><th>Meaning</th></tr></thead><tbody><tr><td>Available</td><td>Free margin available for opening or increasing a position.</td></tr><tr><td>Positions</td><td>Current open position size for the selected market.</td></tr><tr><td>Quantity</td><td>Base-asset amount, such as ETH on <code>ETH/USDC</code>.</td></tr><tr><td>Notional</td><td>Quote value, usually shown in USDC.</td></tr><tr><td>Quantity / Notional slider</td><td>Lets you size from the selected value mode without typing the full amount.</td></tr><tr><td>Reduce only</td><td>Only available when you already have a position. It prevents the order from increasing exposure.</td></tr><tr><td>TP / SL</td><td>Optional take-profit and stop-loss exits created with the entry. They apply to the size of the submitted order.</td></tr></tbody></table>

## Max slippage

<div align="left"><figure><img src="https://1571380119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwUo1o7rINODRyyILQE1%2Fuploads%2Ftsasz2zdAlmdzxFZIkYN%2Fimage.png?alt=media&amp;token=92914a95-68fc-47db-a74a-82236f07f94b" alt="Market order max slippage setting used to protect execution price."><figcaption><p>Market order max slippage setting used to protect execution price.</p></figcaption></figure></div>

On venues with a max slippage control, Proliquid uses the current market price and your setting to derive the worst acceptable price for the order.

The default max slippage is `0.5%` where the control is available. For a long, the protected price is above the current price. For a short, it is below the current price. If liquidity cannot fill within that protected price, the order may partially fill or fail instead of chasing price indefinitely.

## Example flow

1. Select the market in [Terminal](/features/hyperliquid-trading-terminal.md).
2. Choose LONG or SHORT in the [Trade form](/terminal-sections/trade-form.md).
3. Enter quantity or notional.
4. Review reduce-only, TP / SL, and max slippage.
5. Submit and monitor [Positions](/terminal-sections/positions.md), [Trade history](/terminal-sections/trade-history.md), and [Order history](/terminal-sections/order-history.md).

> Final fill depends on available liquidity. Use smaller size, TWAP, or Burst when one order would push too deeply through the orderbook.


---

# 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.proliquid.xyz/order-types/market-orders.md?ask=<question>&goal=<user_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.
