> For the complete documentation index, see [llms.txt](https://infinity-worlds.gitbook.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infinity-worlds.gitbook.io/platform/glossary.md).

# Glossary

* **Warlord** – your unique NFT character on the platform, used to explore expeditions and you can upgrade it with dynamic traits.
* **Traits** – dynamic attributes of your NFT character that impact its rarity and the success rate of passing expeditions.
* **Expeditions** – an interactive map with different regions, each containing multiple stages where players can earn shards and crates.
* **Leaderboard** – a ranking system that ranks users based on the total XP they have accumulated.
* **Infinity Ticket** – WL spot for true Warlords.
* **Shards** – a digital reward earned by successfully passing expeditions and opening crates. They are used to purchase new crates to win another rewards.
* **Rank** – increases with the completion of each 5 levels. Upgrading your rank unlocks access to new expedition regions.


---

# 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://infinity-worlds.gitbook.io/platform/glossary.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.