> 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/6.-use-cases.md). # 6. Use Cases **6.1 Virtual Human Creation** AVIAH.ai allows developers to: * **Design Virtual Characters:** Create customized virtual humans with desired facial features, voices and persona using intuitive authoring tools. * The TTS and V2F module can be customized, and the voice sample and facial expression samples are required for customization. * The visual creation of the virtual character’s face can be as simple as a single (frontal) image. It can be a photo of a real person, cartoon characters or AI generated images through generative AI tools such as SD variants. For more detailed customization, AVIAH.ai can accept multi-view images of the face, and optionally (multi-view) images of facial expressions. * **Select and Fine-Tune LLMs:** Choose from various language models and adjust them to match the desired conversational style. The LLM module can be chosen among chatGPT, Gemini, and Llama. The persona of the created virtual character can be given through system prompts or fine tuning with corresponding API fee rate. * **Deploy to Applications:** Integrate virtual characters into applications such as customer service agents, educational tools, gaming environments, and more in various platforms through SDKs supporting web environments and mobile platforms such as Android and iOS as a Unity3D package. **6.2 API Consumption** AVIAH.ai offers robust APIs for: * **Real-Time Interactions**: Enable applications to interact with virtual characters in real-time with multi-modal inputs such as voices and vision to enable immediate responses from virtual humans. * **AVIAH Token Expenditure**: Each API call consumes AVIAH tokens, ensuring transparency and cost accountability. * **Scalable Services**: Developers can manage token consumption according to their application’s needs. * **Staking for Developers:** * **API Fee Discounts:** Developers who stake AVIAH tokens receive discounted rates on API usage fees, reducing operational costs and incentivizing long-term engagement with the platform. **6.3 Governance** AVIAH holders can influence platform operations through: * **Proposal Submission**: Suggest improvements or new features. * **Voting**: Approve or reject proposals via decentralized voting. * **Community-Driven Evolution**: Staking increases voting power, enabling deeper participation in key decisions. **6.4 NFT Integration** AVIAH.ai integrates NFTs to: * **Represent Virtual Characters**: Each virtual human is minted as a unique NFT, ensuring ownership and authenticity. * **Issue Limited Editions**: Control the scarcity and exclusivity of virtual characters by issuing NFTs in limited quantities (e.g., 100-1000 editions). The NFTs created for a virtual character can be initially distributed to contributors such as portrait right holders, voice right holders, application developers, or investors for the character development. * **Enable Revenue Sharing**: Distribute AVIAH tokens to NFT holders based on the character’s performance. * **Support Marketplace Trading**: Allow NFT owners to trade virtual characters on secondary markets to enhance liquidity and value. **6.5 Staking Benefits** Staking confers distinct advantages on both developers and general users: * **Developers**: * **API Fee Discounts**: Staking AVIAH reduces the cost of API usage, supporting long-term, cost-effective application development. * **General Users**: * **Enhanced Governance Influence**: Staked AVIAH increases voting power, enabling a more impactful role in shaping platform policies and features. --- # 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/6.-use-cases.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.