> For the complete documentation index, see [llms.txt](https://whitepaper.readon.me/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.readon.me/read-fi-token-economy/core-concepts/content-topics-nfts-and-tokens.md).

# Content, Topics, NFTs and Tokens

### Content Quality Standards

ReadON aims to provide **insightful** and **valuable** content to our users. Opinions, in-depth analysis and tutorials will become the primary content.&#x20;

### Topics

Each piece of content on ReadON will be labeled with up to **three** topics by its creator and the process will also be moderated by topic managers.

Initially, there will be around 20 topics created by the ReadON team, as determined by a survey conducted on the ReadON Discord. New topics will need to be created following the process described on the [topic creation page.](/read-fi-token-economy/governance/topic-creation.md)

### Catto NFTs

Catto NFTs are the core assets of ReadON. More details will be described [here](/read-fi-token-economy/core-concepts/catto-nft.md).

### $READ Tokens

$READ tokens are the primary reward that users will earn in ReadON. There is no supply limit for this token.

### $RGT Governance Token

$RGT is the governance token on ReadON. See [Token Distribution](/read-fi-token-economy/token-distribution.md) for more details.


---

# 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://whitepaper.readon.me/read-fi-token-economy/core-concepts/content-topics-nfts-and-tokens.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.
