> For the complete documentation index, see [llms.txt](https://wiki.useace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.useace.com/token-distribution-and-issuance/use-to-earn-reward-pool.md). # Use-to-Earn Reward Pool Incentivizing real usage that shows proof of the value ACE is providing to its users is critical to a growing Product Suite, and rewards for usage are part of ACE’s (not so) secret recipe. Early adopters are pioneers and will be rewarded accordingly. Just like an angel investor takes a bigger percent of the pie relative to their investment as opposed to later-round investors. Use-to-Earn rewards break down into three categories: * Usage * Referral * Payments ### **Usage Rewards** Simple (business-as-usual) usage will reward basic user activity, such as signing up, completing onboarding, or having booked meetings. Each product in the suite will have its own incentive mechanism that will reward usage that is relevant to that product. As activity grows, these rewards will shift towards performance-based rewards. Usage rewards are automatic and will be roughly 60% of the use-to-earn pool. ### **Referral Rewards** To accelerate user growth, signup completion and invites will be incentivized with rewards. If organic growth is rapid enough on its own, these rewards may shift to other areas. Referral rewards are automatic and will be roughly 35% of the use-to-earn pool. ### **Payment Rewards** Financial contributions in the terms of one-time, monthly, or yearly payments for your subscription(s) will earn you payment rewards. Payment rewards are automatic and will be roughly 5% of the use-to-earn pool. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://wiki.useace.com/token-distribution-and-issuance/use-to-earn-reward-pool.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.