> For the complete documentation index, see [llms.txt](https://rgo.gitbook.io/rgo/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rgo.gitbook.io/rgo/official-token/rgo-usdrgo.md). # RGO($RGO) $RGO is the native utility token of the RGO ecosystem. It supports issuance workflows, liquidity mechanisms, creator incentives, and platform-level interactions across both IFO launch modules. RGO is designed to power platform activity, strengthen economic alignment, and sustain long-term ecosystem growth. ### Token Utility #### Issuance Utilities **RGO plays a functional role within the IFO issuance mode:** RGO is supported as a base asset for the initial liquidity pool alongside BNB and USDT. #### Ecosystem Incentives RGO is used across various platform interactions, including: * Creators and video publishers on RGO Shorts * Community engagement and platform activities * Ecosystem campaigns and collaborations #### Premium Features Future platform upgrades may allow RGO to unlock enhanced features such. **RGO aligns the entire RGO lifecycle:** creation → liquidity → exposure → engagement → incentive → repeat. It connects issuers, creators, and users into a unified economic loop powering both IFO launches. --- # 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://rgo.gitbook.io/rgo/official-token/rgo-usdrgo.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.