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

# Player Shares

**Fansports.fun** focuses on featuring high-quality players from Europe’s top competitions, including the **English Premier League, La Liga, Bundesliga, Serie A, and Ligue 1**. This ensures a strong competitive environment and meaningful strategic depth across the platform.

The core design goal is to maintain a constant **sense of opportunity**—every player selection should feel capable of winning, regardless of popularity or market size.

As the platform evolves, the player pool may expand based on **community demand** and overall platform development. In the future, Fansports.fun plans to introduce a **Scouting System**, allowing the community to actively influence which new players are added to the game.

### Shares, Supply & Contracts

* Each player has a **maximum supply of 25,000,000 shares**
* Players are introduced with an **initial supply** allocated at launch
* All player shares are **only tradable on the Fansports.fun Marketplace**
* Every player starts with **4 contracts** when first purchased

This structure ensures controlled supply, transparent trading, and consistent gameplay mechanics across all users.


---

# 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.fansports.fun/getting-started/player-shares.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.