> For the complete documentation index, see [llms.txt](https://omen-protocol.gitbook.io/omen-protocol-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://omen-protocol.gitbook.io/omen-protocol-docs/omen-architecture/platform-architecture.md). # Platform Architecture Understand the architecture behind OMEN Utility, including its application layer, backend service, market data infrastructure, AI analysis, wallet connect, trading integration, and network support OMEN Utility brings market intelligence, AI-assisted analysis, wallet connectivity, and trading integrations together in a unified application. Its architecture connects the user interface with backend services and external infrastructure to support market research and supported trading workflows. **Technical note:** Robinhood Chain deployment details and the availability of individual trading features should be verified against the current implementation before being documented as active capabilities. ### Application Layer The application layer is the primary interface for users interacting with OMEN Utility. It presents market information, token data, analytical tools, wallet connectivity, and supported trading functionality. The interface is designed to help users navigate between research and transaction workflows within one application. ### Backend Services Backend services coordinate requests between the application and external providers. Depending on the feature, these services handle data retrieval, API responses, application logic, and communication with integrated infrastructure. Service availability depends on implementation status and the configuration of the relevant integrations. ### Market Data Infrastructure OMEN Utility uses external data providers to retrieve market and token information. Data availability and accuracy depend on provider coverage, update frequency, supported networks, and API limitations. Differences between providers may occur, and some information may be delayed or incomplete. Market data should be treated as informational and verified independently when accuracy is critical. ### AI Analysis Infrastructure AI-assisted analysis is designed to help users interpret market information and explore crypto-related questions. When configured and available, an external AI service processes user queries and relevant context to generate analytical responses. The quality of these responses depends on the available data, model capabilities, and service configuration. AI-generated content may contain errors, omissions, or outdated information. It does not guarantee market outcomes and should not be treated as financial advice. ### Wallet Connectivity Wallet connectivity enables users to connect supported wallets to access compatible features. Wallet interactions allow users to review transaction details and approve supported operations through their wallet. Actual functionality depends on the connected wallet, supported network, and the integrations available in the current implementation. Users remain responsible for protecting their wallet credentials and reviewing transaction details before signing. ### Trading and Swap Integrations OMEN Utility is designed to connect market research with supported trading workflows, including swap integrations where available. Transaction routes and execution depend on supported assets, available liquidity, routing infrastructure, network conditions, and the services connected to the platform. Displayed quotes may change before execution. Users should independently review transaction details, estimated fees, slippage, and the receiving assets before approving a transaction. A feature should be considered active only when its implementation and availability have been confirmed. ### Network Support Robinhood Chain is the current network focus for OMEN Utility. The platform follows a multichain development direction, with the potential to support additional blockchain networks as the infrastructure evolves. Future integrations depend on technical feasibility, implementation requirements, security considerations, and infrastructure readiness. Additional networks should not be considered supported until their integrations are implemented and confirmed. ### External Dependencies Some OMEN Utility features rely on third-party APIs, AI providers, wallet software, market data services, and trading infrastructure. Changes to external services, API limits, service availability, or network conditions may affect the performance or availability of individual features. OMEN Utility capabilities may therefore vary depending on the configuration and availability of the services required by each feature. ### Architecture Evolution OMEN Utility architecture may evolve as the platform adds integrations, improves existing services, and expands its analytical and trading capabilities. Documentation of new features and network support should reflect the verified implementation status. Planned integrations and future capabilities should be distinguished clearly from features currently available to users. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://omen-protocol.gitbook.io/omen-protocol-docs/omen-architecture/platform-architecture.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.