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

# Improve Rarity

![](/files/-MkcC1vZ9hHwvXO73NBP)

You have the possibility to improve the rarity of an Armz.\
To do so, you need 3 Armz of the same rarity.

Among them, 1 will be upgraded to a higher rarity, and the other 2 will be burned.

If they are Common, then it will become Rare.\
If they are Rare, then it will become Epic.

Epic cannot be upgraded to Legendary.

But, you have a 3% chance of getting an extra upgrade.\
So upgrade a Common to Epic, or a Rare to Legendary!

The cost in PROT varies depending on the rarity of the Armz being fed:

Common: $20 in PROT\
Rare: $30 in PROT

On top of that, 0.05 BNB is added as fee (see [***Tokenomics***](/a/prot/innovative-tokenomics.md) for more information)\
And **50% of these fees will be used to buyback PROT** and fulfil the contract that handles fights rewards.

**All PROT used for Improve Rarity are BURNED.**


---

# 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://armzlegends.gitbook.io/a/improve-rarity.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.