> For the complete documentation index, see [llms.txt](https://docs.trendex.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trendex.gg/4-buying-and-selling-tokens/4.1-buying-tokens.md).
# 4.1 Buying Tokens
#### How swaps work (simple explanation)
When you buy or sell tokens on Trendex, you are performing a swap.
A swap = exchanging one asset for another\
(example: SOL → Token)
The final execution price of a swap can vary slightly due to:
* **Fees (network fees, LP fees)**
* **Slippage (price movement during your transaction)**
* **Liquidity (deep liquidity = more stable price)**
This behavior is standard in AMM-based crypto systems.
Disclaimer:\
\
Trading tokens involves price variability. Trendex does not guarantee execution price, profit, or future value. Users are responsible for understanding swaps and confirming the transaction before submitting.
**You can buy tokens directly inside the Trendex app.**\
\
**You can choose to input:**
* **How much you want to spend (in USD or SOL)**\
**or**
* **How many tokens you want to receive**
Trendex uses Jupiter routing to automatically find the best execution path.
Prices can vary based on:
* **Liquidity depth**
* **Demand at that moment**
* **Price curve positioning**
Once the swap is executed, tokens are instantly credited to your Squad — they appear in your Bench by default (not active yet for the next tournament).
---
# 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.trendex.gg/4-buying-and-selling-tokens/4.1-buying-tokens.md?ask=&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.