> For the complete documentation index, see [llms.txt](https://gameday-squad.gitbook.io/gameday-squad/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gameday-squad.gitbook.io/gameday-squad/tutorial-for-beginners/our-onboarding-tutorial/player-cards.md).

# Player Cards

Collecting cards of your favourite players is at the heart of GameDay Squad and is one of things that makes our platform unique. Each player can be found in every rarity tier, from Bronze to Legend! The higher the tier, the higher that card’s scoring multiplier becomes, but the rarer it becomes to collect! Every card represents real ownership, bringing you closer to the action and letting you feel every play in every game as your Squad comes to life.

<figure><img src="/files/E99pKCGmhhL4i2HvAqMI" alt="" width="375"><figcaption></figcaption></figure>


---

# 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://gameday-squad.gitbook.io/gameday-squad/tutorial-for-beginners/our-onboarding-tutorial/player-cards.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.
