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

# 7. Revenue Model

AVIAH.ai’s revenue is generated through multiple channels, all centered around the AVIAH token:

1. **Token Locking for Virtual Human Creation**
   * Developers acquire and lock AVIAH tokens to create virtual humans, ensuring a stable demand for AVIAH.
2. **API Consumption Fees**
   * Each API call consumes AVIAH, creating a continuous revenue stream tied to service usage levels.
3. **Feature Activation Fees**
   * Developers spend AVIAH tokens to unlock premium features and advanced customization options.
4. **NFT Sales**
   * Limited-edition NFTs representing virtual characters can be sold, providing early funding for the platform.
5. **Revenue Sharing from Services**
   * A portion of the AVIAH tokens in the treasury, accrued from API usage, is redistributed to NFT holders, rewarding community involvement.
6. **Token Burn Mechanism**
   * A percentage of AVIAH used within the ecosystem is permanently burned, thereby reducing supply and potentially boosting value.
7. **Periodic Buybacks**
   * The platform may use part of its revenue to buy back and burn AVIAH tokens, further decreasing supply and supporting its long-term value.
8. **Staking Incentives**
   * By offering staking rewards and API fee discounts, AVIAH.ai encourages holders to remain engaged, promoting a stable and growing ecosystem.


---

# 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://aviah.gitbook.io/aviah-protocol-white-paper/7.-revenue-model.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.