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

# Trading

The trading panel is located on the right side of the token page. It supports both market and limit orders with full control over slippage, priority fees, and MEV protection.

## Buy / Sell Toggle

At the top of the panel, switch between **Buy** and **Sell** modes.

### Market Buy

In market buy mode, you select how much to spend:

* Choose a currency: ETH, USDC, USDT (or the native token of the current chain)
* Enter a custom amount or use the preset buttons (configured in Settings)
* Click **Buy** to execute immediately at market price

<figure><img src="https://3562303282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5bUac2iI3Ns1M4sRzbQ%2Fuploads%2Fgit-blob-72dd70136b0db2bb8ffce2b6721491896a9a3b61%2Fwebapp-trading-buy.png?alt=media" alt="" width="375"><figcaption><p>Trading panel in buy mode with amount presets</p></figcaption></figure>

### Market Sell

In market sell mode, you select what percentage of your holding to sell:

* Preset percentage buttons: 25%, 50%, 100%
* Or enter a custom percentage
* Click **Sell** to execute immediately at market price

<figure><img src="https://3562303282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5bUac2iI3Ns1M4sRzbQ%2Fuploads%2Fgit-blob-c0a4fc331ea52b20aaec0715e55222ef1b558527%2Fwebapp-trading-sell.png?alt=media" alt="" width="375"><figcaption><p>Trading panel in sell mode with percentage presets</p></figcaption></figure>

## Limit Orders

Switch to **Limit** mode to set conditional orders:

* **Target Market Cap** -- set the market cap at which your order triggers
* **Percentage Slider** -- adjust from -100% to +100% relative to current market cap
* Orders execute automatically when the target is reached

<figure><img src="https://3562303282-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE5bUac2iI3Ns1M4sRzbQ%2Fuploads%2Fgit-blob-53aaa541000e78baf5af9ca44c598e6602096f28%2Fwebapp-limit-order.png?alt=media" alt="" width="375"><figcaption><p>Limit order form with market cap target and percentage slider</p></figcaption></figure>

## Trade Settings

Configure execution parameters for each trade:

| Setting            | Options                                                        |
| ------------------ | -------------------------------------------------------------- |
| **Slippage**       | 10%, 20%, 40%, or custom percentage                            |
| **Priority Fee**   | Low, Medium, High, or custom gwei value                        |
| **MEV Protection** | Toggle on/off to protect against sandwich attacks (EVM chains) |

## Position Info

When you hold a position on the current token, the trading panel displays:

* **Bought** -- total amount spent to acquire the position
* **Current Holding** -- current token balance and its USD value
* **PnL** -- profit or loss in both absolute and percentage terms


---

# 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.basedbot.app/web-app/webapp/trading.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.