# Abstract

<figure><img src="https://3465605381-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F6naghnLVqqcefJzJ0l20%2Fuploads%2FnvCJXw5QaiAjyF1b35YT%2FWP%20ABSTRACT.png?alt=media&#x26;token=6c51eefc-6763-4622-8251-8521de92a591" alt=""><figcaption></figcaption></figure>

Ruvi is a decentralized AI superapp that combines cutting-edge artificial intelligence tools and Web3 technology into a unified, accessible platform. Designed for creators, professionals, and developers, Ruvi integrates multiple AI capabilities—text generation, image creation, video synthesis, and sound production—within a seamless user experience. In addition to on-demand AI tools, Ruvi offers a library of customizable templates for various content needs, from blog posts and social media assets to academic writing and business material.

Ruvi is powered by a native utility token ($RUVI), which fuels the ecosystem and incentivizes user participation. The token will be launched via a multi-phase presale to raise capital for development, infrastructure, and marketing. Beyond its functional role, $RUVI serves as a reward mechanism in a novel user-in-the-loop training system, where community members can contribute to the improvement of Ruvi’s native AI models by providing feedback, annotations, and training data.

By combining AI, community participation, and decentralized finance, Ruvi sets out to democratize access to advanced content-generation tools while building a sustainable, user-driven ecosystem.


---

# Agent Instructions: 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://docs.ruvi.io/abstract.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.