> 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/faq/usdomen-token.md). # $OMEN Token Learn about $OMEN tokenomics, utility, holder benefits, AI access, and the role of the token within OMEN Protocol. This page answers common questions about $OMEN, including tokenomics, ecosystem utility, holder benefits, and planned AI access. ### 1. What is $OMEN? $OMEN is the ecosystem token for OMEN Protocol. It is designed to support platform utility and future ecosystem features. ### 2. What is the total supply of $OMEN? The total supply of $OMEN is **1,000,000,000 tokens**. ### 3. How is the $OMEN supply allocated? **PONS Launchpad Allocation:** 95% of the total supply, equivalent to 950,000,000 tokens. **Developer Allocation:** 5% of the total supply, equivalent to 50,000,000 tokens. Any developer token lock or vesting arrangement will be confirmed through official announcements. ### 4. What is the utility of $OMEN? $OMEN is intended to support utility across the OMEN Protocol ecosystem. Planned use cases include holder-based access to AI features and potential utility within future platform services. Additional utility may be introduced as the platform develops. ### 5. Can $OMEN holders access AI Analyst? OMEN Protocol plans to introduce token-based access tiers for AI Analyst. The proposed system may provide different usage allowances based on eligible $OMEN holdings. Final requirements and usage limits will be announced when the system is ready. ### 6. How many $OMEN tokens are required for AI access? A starting threshold of **100,000 $OMEN** has been discussed for a potential access tier. This threshold is not a confirmed active requirement. Final holding thresholds and access rules will be published through official announcements. ### 7. What are OMEN holder badges? OMEN holder badges are a planned way to represent access tiers within the ecosystem. Depending on the final design, badge levels may correspond to eligible token holdings and AI usage allowances. Badge names, eligibility requirements, and benefits remain subject to confirmation. ### 8. Do higher holding tiers provide more AI usage? The planned tier system may offer different AI usage limits according to eligible token holdings. Exact tier thresholds and daily limits have not been finalized. Refer to official OMEN announcements for confirmed details. ### 9. Does holding $OMEN guarantee profits? No. Holding $OMEN does not guarantee profits, price appreciation, or financial returns. Crypto assets involve risk, and users should conduct independent research before making financial decisions. ### 10. Where can I find official token information? Check official OMEN Protocol communication channels for verified token details, contract information, and utility updates. Always verify the token contract address and network before interacting with $OMEN. ### 11. Will $OMEN gain additional utility? Additional utility may be introduced as OMEN Protocol expands. New features and token mechanisms will depend on implementation and official announcements. Show less --- # 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/faq/usdomen-token.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.