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

# ⚡ Token Utility

### 1. 🏗️ <mark style="color:$primary;">Publishing Engine</mark>

Authors use RICO to publish content.

* **100 RICO** is used per listing
* listing activity contributes to recurring token utility
* listing fees are designed to support scarcity through burn logic

> 📚 More content can mean more RICO utility.

### 2. 💳 <mark style="color:$primary;">Transaction Layer</mark>

RICO is also used as part of book purchase activity.

* **5 RICO** is used per purchase
* purchase activity connects token utility directly to user demand

> 👥 More readers can mean more recurring token use.

### 3. 🗳️ <mark style="color:$primary;">Decentralized Curation</mark>

Community members can use RICO in curation systems such as:

* voting on books
* voting on authors

This creates an economically meaningful quality layer for the ecosystem.

### 4. 💰 <mark style="color:$primary;">Yield & Staking Utility</mark>

Holders can stake RICO to access:

* APY-based rewards
* bonus incentives
* redistribution rewards
* compounding strategies
* airdrop eligibility

This turns RICO into productive ecosystem capital.

### 5. 🔐 <mark style="color:$primary;">Access Economy</mark>

Purchased content can be represented through soulbound access models.

That means RICO supports a broader Web3-native ownership infrastructure tied to education and publishing.

### 6. 🎁 <mark style="color:$primary;">Loyalty and Ecosystem Rewards</mark>

Holders and stakers may also qualify for reward layers such as:

* airdrops
* ecosystem incentives
* future participation systems

<mark style="color:$success;">Next: 🔄 Token Utility Flywheel</mark>


---

# 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://rico-matrix.gitbook.io/whitepaper/token-utility.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.