> 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.md).

# RAKE Ecosystem

RAKE's X bot, dApp, real-time leaderboard, and RakeVault components.

## One ecosystem, two interfaces

RAKE has two faces and one lane. The X bot and dApp are entry points into the same RAKE lifecycle. They do not create separate products or fee paths.

The X bot is the command and interaction layer. The dApp is the visual and information layer. Supporting systems make launched-token activity and fee flow visible.

```
User
├── X Bot (@rake_agent)
│   ├── launch
│   ├── harvest
│   ├── tip
│   ├── swap
│   ├── buy
│   ├── burn
│   ├── buyback
│   ├── bridge
│   └── predict
│
└── dApp
    ├── leaderboard
    ├── token pages
    ├── harvest panel
    └── prediction market UI
```

### The shared lifecycle

Launches enter through Pons V2 with RakeVault configured as the fee recipient. Every launched token appears on the Leaderboard. Harvest moves accumulated fees into RakeVault. The defined fee split then routes the creator allocation and market-buy burn allocations.

```
Launch
    ↓
Pons V2
    ↓
RakeVault
    ↓
Leaderboard
    ↓
Harvest / fee flow
```

The bot can initiate supported actions through commands. The dApp adds visual context through token pages, the leaderboard, the harvest panel, and the prediction market UI. Information and actions therefore remain connected across the same RAKE system.

### Ecosystem components

| Component   | Role in RAKE                                      |
| ----------- | ------------------------------------------------- |
| X Bot       | Command and interaction layer                     |
| dApp        | Visual and information layer                      |
| Leaderboard | Visibility for launched tokens and their activity |
| RakeVault   | Fee-routing and distribution destination          |

Use [X Bot](/rake/rake-ecosystem/x-bot.md) for command-based interaction. Use [dApp](/rake/rake-ecosystem/dapp.md) for visual context. See [Leaderboard](/rake/rake-ecosystem/leaderboard.md) for token activity, and [RakeVault](/rake/rake-ecosystem/rakevault.md) for fee flow.


---

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