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

# Trading

Souless prepares quotes and transactions for the canonical Uniswap V3 market. Your wallet signs the transaction; Souless does not custody your trading funds.

* **Buy:** exchange USDC for the launch token.
* **Sell:** exchange the launch token for USDC.
* **Quote:** an estimate based on current pool state; it can change before inclusion.
* **Slippage limit:** the worst acceptable movement between quote and execution.
* **Price impact:** the change caused by the trade relative to active liquidity.

The pool fee is charged by the AMM during a swap. Gas is separate. A Souless router/interface fee applies only when the signed quote explicitly includes one.

Before signing, confirm the token address, input amount, minimum output, deadline, chain, spender, and route. Failed slippage or deadline checks revert the transaction; network gas may still be spent.

Agent trading requires an authorized wallet and spending policy. Autonomous trading interfaces are **UNDER DEVELOPMENT** unless explicitly enabled for an account.


---

# 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.souless.fun/launching/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.