> For the complete documentation index, see [llms.txt](https://docs.ypredict.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ypredict.ai/ypredict-token/tokenomics/utilities.md). # Utilities yPredict offers three primary features through its platforms; marketplace, trading tools, trading terminal, and high APY% staking pools.\ \ Within the yPredict ecosystem, YPRED holders can do the following with their tokens. * Free access to yPredict analytics platform to analyze coins using data-driven insights & metrics. * Pay for predictive model subscriptions through yPredict Marketplace * Get incentivized for votes on the marketplace * Earn lucrative APYs by participating in staking. Unlike the majority of staking pools, it doesn’t have fixed liquidity from an allocated token supply. The Source of liquidity for these pools is 10% of each new user's YPRED deposit which keeps APYs consistent. --- # 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://docs.ypredict.ai/ypredict-token/tokenomics/utilities.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.