> For the complete documentation index, see [llms.txt](https://doc.metarun.game/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.metarun.game/metarun-economy/5.6-earning-potential.md).

# 5.6 Earning Potential

* Earning potential of every character is associated with the\
  a. Rarity of the characters. \
  b. The rarity of skin. \
  c. Win rate. \
  d. Hero league.
* The higher the character rarity, skin rarity, and win rate, the higher the earnings potential.
* Heroes with a higher rarity will have more powerful abilities, initial characteristics ( health, mana potion, damage, max speed), and higher win/lose bonuses resulting in higher earning potential.
* Heroes with a higher skin rarity will have a higher character level, character active and passive abilities power level, and OPAL earning battles results in higher earning potential.

  The character with higher rarities has more chances to win the PvP battles resulting in higher earning potential.
* The higher the hero league, the higher the rewards will be in every match and at the end of every season, resulting in higher earning potential.


---

# 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:

```
GET https://doc.metarun.game/metarun-economy/5.6-earning-potential.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.