> 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/token-and-ecosystem/omen-usecase.md). # Omen Usecase Explore how $OMEN support AI access, OMEN Listed submission, token burn, and ecosystem development. $OMEN is the utility token associated with the OMEN Protocol ecosystem. Its intended role is to connect token utility with platform access, project submissions, and ecosystem development. ### AI Access $OMEN is intended to support holder-based access to selected AI features through a planned badge or tier system. Different tiers may provide different AI usage allowances or platform privileges. Holding requirements, daily query limits, and eligibility rules will be published once the access system is finalized and active. Until then, proposed tier benefits should not be treated as active entitlements. ### OMEN Listed Submissions $OMEN is proposed as a payment token for project submissions through OMEN Listed. Submission fees, payment procedures, eligibility requirements, and refund terms will follow the official policy published for the service. Submitting a project does not guarantee approval or listing. All applications remain subject to the OMEN Listed review process. ### Ecosystem Revenue Allocation OMEN Protocol plans to allocate eligible revenue generated from swap activity and OMEN Listed submissions toward two purposes: **50% — Token Burn** The designated portion is intended to fund the burning of $OMEN, permanently removing tokens from circulation when the burn is executed. **50% — Research and Development** The remaining portion is intended to support product development, infrastructure, research, and improvements across the OMEN ecosystem. This allocation model is intended to connect platform activity with token supply reduction and long-term ecosystem development. Actual allocations depend on the final implementation and eligible revenue generated. The planned split does not guarantee revenue, a specific amount of tokens burned, or a particular rate of supply reduction. ### Token Burn Mechanism The planned token burn mechanism is intended to reduce the circulating supply of $OMEN through verifiable onchain transactions. Actual burns depend on eligible revenue and execution of the mechanism. Completed burns should be documented through official announcements and verifiable onchain records when available. Until the mechanism is implemented and verified, the planned burn allocation should not be interpreted as completed burn activity. ### Research and Development The research and development allocation is intended to support the continued development of OMEN Protocol. Potential areas include: 1. Improvements to OMEN Utility and market intelligence. 2. Development and maintenance of AI-powered tools. 3. Integration of additional networks and services. 4. Infrastructure, reliability, and platform improvements. 5. Research into future products and token utility. These areas describe the intended development direction and do not imply that every feature or integration is currently available. ### Long-Term Utility OMEN Protocol aims to connect $OMEN utility with actual platform usage. AI access, project submission payments, and the planned revenue allocation model are intended to form part of this ecosystem. Additional utility may be introduced as the platform develops. New features, access requirements, and revenue mechanisms will be documented when officially confirmed. ### Important Notes Token utility and ecosystem mechanisms may evolve as OMEN Protocol develops. Refer to official documentation for current AI access rules, OMEN Listed submission terms, and the status of the token burn mechanism. Holding $OMEN does not guarantee profits, project listing approval, AI access beyond applicable rules, or any particular market outcome. --- # 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/token-and-ecosystem/omen-usecase.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.