# Maneki’s Sub-Agents ### Maneki’s Sub-Agents Behind the intuitive interface of Maneki lies a network of sub-agents, each working in harmony to power your decentralized wealth journey. This orchestrated architecture allows Maneki to support a wide variety of use cases for retail, B2B, and agent-to-agent interactions. These sub-agents are responsible for: * Scanning your wallet and identifying idle assets. * Analyzing the entire DeFi landscape to discover yield flows specifically tailored to your portfolio and goals. * Assessing and comparing the risks associated with various yield strategies and protocols, providing you with transparent insights. * Gathering in-depth analytical information on yield strategies. * Constructing investment reports by pulling data from media, social platforms like X, and dedicated analytical platforms to evaluate protocol health. * Building complex cross-chain transactions that allow you to enter any strategy seamlessly from any asset in your wallet. * Calculating gas costs and price impact for every transaction, ensuring optimal execution. * Explaining complex DeFi concepts in an accessible way, simplifying your understanding of the technology. * Supporting a vast array of other specialized functions to enhance your experience. Our initial release of Maneki was a chat-bot, which allowed us to consolidate all these foundational building blocks into one accessible place for users to explore. We're now leveraging this robust core to develop even more user-centric products. --- # 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.helios.space/architecture/manekis-sub-agents.md?ask= ``` 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.