> For the complete documentation index, see [llms.txt](https://docs.rakelaunch.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rakelaunch.xyz/rake/introduction/overview.md). # Overview RAKE's independent launchpad role on Robinhood Chain and its use of Pons V2 for launch exposure. RAKE is an independent launchpad on Robinhood Chain. It uses Pons V2 as the launch venue for exposure to the Pons community. RAKE stands on its own. It is not a subsidiary, wrapper, or feature inside another product. The systems that extend activity beyond launch belong to RAKE, including its vault, harvest, burn, Echo, and leaderboard systems. ### One ecosystem, two interfaces RAKE has two connected interfaces: * The X bot, `@rake_agent`, supports RAKE actions through X. * The dApp provides visual interfaces for the leaderboard, token pages, harvest panel, and prediction markets. These are not separate products. They are two ways to access the same RAKE ecosystem. > **Two faces, one lane.** An action can begin through X and continue in the dApp. An action that starts in the dApp can also continue through X. This shared path connects conversational execution with visual protocol interfaces. RAKE therefore begins with launch exposure, but it does not stop there. The next question is why launch needs an ecosystem around the activity that follows. --- # 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.rakelaunch.xyz/rake/introduction/overview.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.