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

# Market Orders

**Market is the at-current-price order mode — fastest path to execution, with the trade-off that the price you click isn't necessarily the price you get.**

A market order takes the best available price on the book at the moment the transaction lands. There's no waiting for a level; there's no canceling once it's in flight. Use Market when execution speed matters more than precision, and Limit when precision matters more than speed (see [Limit Orders](/graphdex-docs/trading/limit-orders.md)).

{% hint style="success" %}
**Speed first, precision second**

Use Market when you want the trade *now* — the trade-off is that the fill price can differ from the screen price, especially on thin liquidity.
{% endhint %}

## THE MARKET PANEL

The order panel exposes the same surface for Buy and Sell — the only difference is the side toggle.

* **Buy / Sell** — order side.
* **Market / Limit** — order type (Market here).
* **Balance** — your available balance for the order.
* **SOL amount input** — the size of the trade.
* **Quick amount buttons** — preset SOL sizes for Buy (`0.01`, `0.25`, `0.5`, `1`).
* **Priority** / **Bribe** / **Slippage** — execution levers from [Trading Settings](/graphdex-docs/trading/trading-settings-overview.md).
* **Slow / Fast / Turbo** presets — write a coherent execution profile in one tap.

## BEFORE PLACING A MARKET ORDER

A six-line check that catches most avoidable failures.

* Confirm the **token** and **pair** on the header.
* Check **LIQ**, **MC**, **5M Vol** on the same header.
* Skim recent **Transactions** — is the flow one-sided?
* Read **Top holders** and the **Token details** strip.
* Confirm **Slippage**, **Priority**, **Bribe** match what you want for this order.
* Confirm the **wallet** and **balance** are right.

## EXECUTION RISK

Market doesn't promise the screen price. A few specific failure modes to expect:

* Price moves between click and confirmation — your fill ends up worse than displayed.
* Thin liquidity amplifies the drift — same trade size, much larger slippage hit.
* Volatile conditions can cause the order to **fail** rather than execute.
* Aggressive Priority / Bribe settings increase cost without guaranteeing inclusion.
* See [Slippage](/graphdex-docs/trading/slippage.md), [Risk of Fast Execution Settings](/graphdex-docs/trading/risk-of-fast-execution-settings.md), and [Execution Risks](/graphdex-docs/trading/execution-risks.md).

{% hint style="warning" %}
GraphDex provides the order tools — it doesn't guarantee final execution price, transaction success, or block inclusion. Read the risk pages before placing aggressive market orders.
{% endhint %}

## FAQs

<details>

<summary>What's the difference between Market and Limit?</summary>

* **Market** — execute at the best available price now.
* **Limit** — wait for the market to reach the price you set, then execute.

See [Limit Orders](/graphdex-docs/trading/limit-orders.md) for the Limit variant.

</details>

<details>

<summary>Why might my Market fill price differ from the screen price?</summary>

Because the price moves between click and confirmation, especially on thin LIQ or in volatile conditions. **Slippage** is the tolerance you allow for that drift — set too tight and the order rejects, set too wide and you can fill at much worse than the screen price.

</details>

<details>

<summary>What do the quick amount buttons set?</summary>

For Buy mode, they prefill the SOL amount input with `0.01`, `0.25`, `0.5`, or `1` SOL. They're shortcuts only — you can override the value before sending.

</details>

<details>

<summary>What do Slow / Fast / Turbo change?</summary>

They write coherent Priority / Bribe / Slippage profiles into the panel. Per-order overrides still apply. See [Presets and Quick Suggestions](/graphdex-docs/trading/presets-and-quick-suggestions.md) and [Trading Settings Overview](/graphdex-docs/trading/trading-settings-overview.md).

</details>

<details>

<summary>Can a Market order fail to execute?</summary>

Yes. In volatile conditions, with insufficient priority/bribe, or if slippage is too tight for the conditions, an order can fail rather than execute. See [Execution Risks](/graphdex-docs/trading/execution-risks.md).

</details>


---

# 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://graphdex-1.gitbook.io/graphdex-docs/trading/market-orders.md?ask=<question>&goal=<endgoal>
```

`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.