> 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/rake-ecosystem/dapp.md).

# dApp

RAKE's dApp interface and its connection to actions initiated through the X bot.

## Visual interface

The dApp is RAKE's visual-first interface. The X bot is mobile-first. Both connect to the same RAKE ecosystem.

The dApp provides visual context around launched tokens, leaderboard information, harvest, and prediction markets. It is not a separate product or separate protocol path.

### Documented surfaces

| Surface              | Role                                                     |
| -------------------- | -------------------------------------------------------- |
| Leaderboard          | Displays launched-token activity and fee-related metrics |
| Token pages          | Provides context for launched tokens                     |
| Harvest panel        | Provides a visual harvest interface                      |
| Prediction market UI | Provides a visual prediction-market interface            |

### Launch from the dApp

```
rakelaunch.xyz/launch → fill form → deploy
```

The dApp starts the documented launch flow. Deployment proceeds through Pons V2 with RakeVault as the fee recipient.

### Two entry points, one system

The interfaces support different ways to enter RAKE. They remain connected to the same underlying lifecycle.

```
X Bot
    ↓
command
    ↓
RAKE system
    ↓
dApp visibility
```

```
dApp
    ↓
visual interaction
    ↓
RAKE system
    ↓
continued interaction through X
```

The dApp does not imply that every RAKE action exists in both interfaces. It provides the documented visual surfaces, while [@rake\_agent](https://x.com/rake_agent) provides supported command interaction.


---

# 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/rake-ecosystem/dapp.md?ask=<question>&goal=<endgoal>
```

`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.