> For the complete documentation index, see [llms.txt](https://myros.gitbook.io/bp/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://myros.gitbook.io/bp/applications/use-cases.md). # Use Cases
Myros is built for projects that need fast, reliable, project-specific answers. She can serve as the knowledge layer for communities, products, teams, and ecosystems. *** #### Web3 Communities Web3 projects move quickly. Users need answers about tokens, staking, governance, roadmaps, partnerships, documentation, and ecosystem updates. Myros can help Web3 teams reduce repeated questions and give users direct access to trusted project knowledge. | Need | Myros Function | | -------------------- | ------------------------------------------- | | Community support | Answers common project questions | | Documentation access | Retrieves information from official sources | | Governance education | Explains proposals and processes | | Ecosystem onboarding | Guides new users through project basics | | Real-time updates | Pulls from approved live sources | *** #### Gaming Projects Games require constant communication across updates, systems, lore, events, and player support. Myros can act as a player-facing knowledge agent for game communities. | Need | Myros Function | | -------------------- | --------------------------------------------- | | Player onboarding | Explains how to start | | Game guides | Answers questions about mechanics | | Lore access | Provides world and character context | | Patch support | Summarizes latest updates from official pages | | Community assistance | Reduces repeated support questions | *** #### Open-Source Projects Open-source projects often rely on documentation, GitHub issues, contribution guides, and community support. Myros can help contributors find the right information faster. | Need | Myros Function | | ---------------------- | ---------------------------------------- | | Contributor onboarding | Explains setup and contribution steps | | Documentation support | Answers from official docs | | Repository guidance | Helps users understand project structure | | FAQ automation | Handles common technical questions | | Community scaling | Reduces maintainer support load | *** #### Startups and Product Teams Startups need to support users while moving fast. Myros can serve as a lightweight product knowledge agent for customers, users, and internal teams. | Need | Myros Function | | ------------------ | -------------------------------------- | | Product questions | Answers from product pages and docs | | Customer support | Handles repeated support requests | | Internal knowledge | Helps teams access process information | | Sales enablement | Explains features and use cases | | Onboarding | Guides new users or employees | *** #### DAOs and Digital Communities DAOs and online communities depend on shared knowledge, proposals, rules, and coordination. Myros can help members understand what is happening without searching through scattered discussions. | Need | Myros Function | | --------------------- | --------------------------------------------- | | Proposal discovery | Explains governance proposals | | Member education | Answers community process questions | | Rule access | Retrieves community guidelines | | Historical context | Uses stored conversation and approved sources | | Participation support | Helps users understand how to contribute | *** #### Internal Knowledge Agents Teams lose time searching for information across documents, websites, and chats. Myros can be deployed as an internal agent for fast access to operational knowledge. | Need | Myros Function | | ---------------- | --------------------------------------- | | Team support | Answers internal process questions | | Knowledge access | Retrieves from approved company sources | | Training | Helps onboard new team members | | Operations | Explains workflows and procedures | | Productivity | Reduces time spent searching |