> For the complete documentation index, see [llms.txt](https://fcm-1.gitbook.io/fcm-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fcm-1.gitbook.io/fcm-docs/how-users-trade.md).

# How Users Trade

**Predict & Back Your Favorites**

* Support your **team**: build a portfolio of your club’s players.
* Support your **player**: buy tokens and ride their form.
* Support a **game**: trade on live match action.
* Support a **season**: hold for long-term growth.

You’re not just watching football anymore -> you’re trading it.

**3.2 Before the Match**

* Buy undervalued players who might perform well.
* Example: Forward looks sharp, undervalued vs true worth → buy ahead.

**3.3 During the Match**

* React to live action:
  * Goal scored → price spikes.
  * Injury → price dumps.
  * Red card → sell pressure.
* Short-term traders thrive on volatility.

**3.4 After the Match**

* Rebalance portfolio.
* Hold long-term on rising stars.
* Switch out of players dropping in form.

[<br>](https://fcm.gitbook.io/fcm.fun/how-tokens-work)


---

# 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://fcm-1.gitbook.io/fcm-docs/how-users-trade.md?ask=<question>&goal=<endgoal>
```

`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.