> For the complete documentation index, see [llms.txt](https://elindos-phar.gitbook.io/exode-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elindos-phar.gitbook.io/exode-white-paper/white-paper/valuation.md).

# Valuation Policy

EXODE has a "Positive Valuation Policy" made of the following points:\
\
**1) Scarcity**\
\
EXODE proposes limited editions of packs, in time and quantity, thus ensuring scarcity.\
\
\
**2) Increasing shop price over time**\
\
EXODE increases shop price of its packs over time, pushing their value upwards and allowing players to "undercut the shop" for all distributed packs.\
\
This is a main point invoked when mentioning "our Valuation Policy".\
\
\
**3) Large collection with many unique references and game design layers**\
\
EXODE collection is large and multilayered, ensuring that your individual collection always has some identity and usage, while also ensuring that collecting every possible card is still interesting but also a huge endeavour for players, involving multiple players, multiple collections, and multiple trades. \ <br>


---

# 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://elindos-phar.gitbook.io/exode-white-paper/white-paper/valuation.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.