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

# Order Settings

These settings let you fine-tune how your orders are executed. Use them to reduce failed trades, limit fees, and improve execution speed.

{% tabs %}
{% tab title="Basic Settings" %}

* **Slippage** – Set the max price difference you're willing to accept to prevent failed trades due to volatility.
* **Additional Gas Price** – Add a small gas buffer to prioritize your transaction during high activity.
* **MEV Protection** – Shields your trades from MEV bots (e.g., sandwich attacks that exploit price changes right before your trade). 

{% hint style="info" %}
Available only for trades on Solana
{% endhint %}

* **Auto-Approve** – Automatically gives token approval after purchase, which saves time on future trades.
  {% endtab %}

{% tab title="Solana Gas Settings" %}
Solana allows you to pick a gas speed mode depending on your needs:

* **Normal** – Standard speed and cost. Ideal for casual trading.
* **Fast (+300%)** – Speeds up transaction confirmation by paying 3x standard fees.
* **Degen (+900%)** – Maximum speed for urgent trades.
* **Custom** – Manually adjust gas fees to your own preference.
  {% endtab %}
  {% endtabs %}


---

# 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.lab.pro/order-settings.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.