> 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/2-the-game/2.3-squad.md).
# 2.3 Squad
Your Squad is where your Tokens live.
When you buy Tokens, they automatically enter your Squad.\
This is your inventory, your pool of players.
But having Tokens in your Squad is not enough to compete.\
To actually use them inside a tournament, you need to activate them.
The Squad is simply the list of all the Tokens you own, both Official and Community, whether they are activated or not.
***
#### Key concept
* **Squad = your total holdings**
* **Active players = Tokens you have specifically activated for the current tournament**
Only your activated Tokens will score points.
The Squad is the base layer.\
Then you decide which players you deploy for each tournament.
***
#### Why this matters
The Squad allows you to:
* **scout players over time**
* **build long-term conviction**
* **accumulate exposure across leagues and skill profiles**
* **decide which positions you want to play for each cycle**
Trendex is not random, it is selection + conviction.\
**Your Squad represents your football thesis.**
---
# 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://docs.trendex.gg/2-the-game/2.3-squad.md?ask=&goal=
```
`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.