> For the complete documentation index, see [llms.txt](https://docs.apex-ai.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apex-ai.ai/appendix/tokenomics.md). # Tokenomics Clear tokenomics and full transparency are essential for building real trust with our community. Here's a detailed breakdown of how we're allocating [$APEX](https://x.com/search?q=%24APEX\&src=cashtag_click) tokens, so everyone is on the same page from day one: **Market (60%)** \- Fully allocated to the community through public distribution. **Startup R\&D (15%)** \- Dedicated primarily to further R\&D and clinical validation in the US to secure FDA approval. \- Vesting: 1% unlocked at TGE; remaining 14% after a 30-day cliff, then linearly vested over 150 days. D-Day **Operations (10%)** \- Supports the broader D-Day ecosystem, incubation services, and strategic growth. \- Vesting: 1% unlocked at TGE; remaining 9% after 30-day cliff, linearly vested over 150 days. **Marketing & Partnerships (6%)** \- Key Partners: 25% unlocked at TGE, remaining 75% linearly vested over 180 days. \- Community Airdrops & Rewards: Fully unlocked at TGE. **Treasury (9%)** \- Reserved for future partnerships, CEX listings, and operational expenses. \- 3% unlocked at TGE exclusively for CEX listings. \- Remaining 6% after 30-day cliff, vested linearly over 365 days. \- Transparent reporting of every treasury transaction on Discord. Minimal Dump Risk: - Only 5% of internal allocations are circulating at TGE (including partnerships, community airdrops and rewards) significantly minimizing sell-off risk. \- Locked allocations stored securely in multisig wallets with transparent on-chain vesting.
--- # 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://docs.apex-ai.ai/appendix/tokenomics.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.