> For the complete documentation index, see [llms.txt](https://atronprotocol.gitbook.io/atron/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atronprotocol.gitbook.io/atron/risk-levels.md). # Risk Levels **Earn Rewards at any Level!** The ATRON ecosystem has two risk levels when it comes to potential token appreciation/depreciation and potential rewards, but **both levels could earn the holder rewards from the activity of the market**. * **Higher Risk / Higher Reward Potential - ATRON** * ATRON is considered a low market cap token, where high volatility is present. Low market cap tokens are where users have see their holdings go up 10x, 100x or even 1000x in a very short period of time, but is also where they can see the biggest loses, including total loss in some scenarios. * **Lower Risk / Lower Reward Potential - AUSD** * AUSD is a stable token, meaning that the price will always be pegged to one dollar ($1.00), giving users peace of mind that their holdings will keep the same value over time. Stable assets are used to facilitate cross-border remittances, allowing people to send and receive money with lower fees and faster settlement times. They are also used to avoid price movement of your holdings. --- # 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://atronprotocol.gitbook.io/atron/risk-levels.md?ask=&goal= ``` `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.