> For the complete documentation index, see [llms.txt](https://whitepaper.xerians.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.xerians.com/game-mechanics/xerian-types-and-rarity/xerian-soldiers-rare-epic-gold.md).

# Xerian Soldiers (Rare/Epic/Gold)

<figure><img src="/files/ViSp21GShyND4EKbLBye" alt=""><figcaption></figcaption></figure>

Xerian Soldiers are ready to do whatever it takes to win their fights. They are separated into 9 layers (5 body parts, 1 card color and 3 boosters). Cards will be Gold, Ruby or Emerald. During the minting; the layers, the cards and the boosters will be generated randomly.

They have 3 types of rarity scores according to the leaderboard between Xerian Soldiers according to their total skill score:

* Rare \[x1760] – with Emerald card
* Epic \[x3500] – with Ruby card
* Common \[x5500] – with Gold card


---

# 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://whitepaper.xerians.com/game-mechanics/xerian-types-and-rarity/xerian-soldiers-rare-epic-gold.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.
