> 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/getting-started/introduction.md). # Introduction Overview of OMEN Protocol, its core product, token utility, and vision for a connected multichain crypto ecosystem. ### Overview OMEN Protocol is a crypto intelligence platform that brings market data, on-chain insights, AI assisted analysis, and trading tools into one unified experience. The platform is designed to help users explore digital assets, understand market activity, and access trading functionality without relying on disconnected tools for every step of the process. OMEN combines market discovery, analytical capabilities, and integrated token swaps within a growing ecosystem focused on practical utility and long-term development. ### The Platform Crypto markets operate across multiple networks, data sources, and trading venues. Finding relevant information and acting on it often requires switching between different platforms. OMEN Protocol aims to simplify this experience by bringing essential market intelligence and trading capabilities together. The current platform focuses on crypto market data, token discovery, AI-assisted analysis, wallet connectivity, and token swaps on supported networks. Additional capabilities are planned as the platform develops. ### Core Capabilities #### Market Intelligence Explore digital assets, market activity, token information, and available liquidity across supported markets. OMEN aims to provide a more accessible view of the information users need when researching crypto assets. #### AI Analyst AI assisted analysis helps users investigate tokens and interpret available market information. Its output should be treated as analytical assistance rather than financial advice or a guarantee of market outcomes. #### Integrated Trading OMEN Utility includes token swap functionality for supported assets and networks. Users connect their own wallets and authorize transactions themselves. Availability, execution routes, and transaction costs depend on the selected asset and network. #### Multichain Development OMEN is being developed with a broader multichain direction. The objective is to expand market coverage and connect intelligence with trading functionality across additional blockchain ecosystems over time. ### The $OMEN Token $OMEN is the ecosystem token associated with OMEN Protocol. The project intends to develop token utility around platform access and selected ecosystem benefits. Holder access, eligibility requirements, and usage limits will be documented separately as those features are finalized and implemented. Planned benefits should not be interpreted as active functionality until officially announced. ### Looking Ahead OMEN Protocol is focused on building useful infrastructure for crypto market research and trading. Development priorities include improving the existing utility, expanding market coverage, and introducing additional ecosystem features when they are ready. Detailed development phases are pending confirmation. The roadmap may evolve with technical requirements, integrations, and market conditions. --- # 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/getting-started/introduction.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.