> 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/commands-and-assets/commands.md).

# Commands

Source-defined RAKE command syntax, supported actions, and unsupported action boundaries.

RAKE is multi-verb, not launch-only. Use [@rake\_agent](https://x.com/rake_agent) for the documented X command interface.

| Verb      | Function                                                  | Echo |
| --------- | --------------------------------------------------------- | ---- |
| `launch`  | Deploy a new token on Pons V2                             | No   |
| `harvest` | Pull accumulated fees to RakeVault, auto-split, auto-burn | No   |
| `swap`    | Trade assets through the RAKE router                      | Yes  |
| `tip`     | Send an asset to another user                             | Yes  |
| `buy`     | Buy a token with ETH                                      | Yes  |
| `burn`    | Burn the user's own tokens                                | Yes  |
| `buyback` | Buy a token and then burn it                              | Yes  |
| `bridge`  | Bring ETH from outside into Robinhood                     | Yes  |
| `predict` | Create a YES/NO prediction market                         | No   |

### No-Echo commands

#### `launch`

```
@rake_agent launch $MOON "MoonShot" pair ETH
```

Deploys a new token on Pons V2. RAKE routes its fee recipient to RakeVault. The launched token then appears on the RAKE leaderboard.

#### `harvest`

```
@rake_agent harvest $MOON
```

Harvest is permissionless. Anyone can trigger it.

It pulls accumulated fees from the relevant curve, hook, and escrow sources into RakeVault. The vault applies the 70/15/15 distribution and the automatic buy-and-burn behavior.

#### `predict`

```
@rake_agent predict NVDA >150 Friday
```

Creates a YES/NO prediction market around the specified outcome.

The supported verb set contains nine commands. It does not define separate `unclaimed` or `alive` commands.

### Echo-required commands

Each action below can move assets. It requires Echo confirmation before execution.

#### `tip`

```
@rake_agent tip @user 2 NVDA
```

Sends the specified asset to another user after Echo confirmation completes.

#### `swap`

```
@rake_agent swap 0.05 ETH to $PONS
```

Trades assets through the RAKE router after Echo confirmation completes.

#### `buy`

```
@rake_agent buy 0.05 ETH of $MOON
```

Buys a token with ETH after Echo confirmation completes.

#### `burn`

```
@rake_agent burn 1000 $RAKE
```

Burns the user's own tokens after Echo confirmation completes.

#### `buyback`

```
@rake_agent buyback 0.02 ETH of $MOON then burn
```

Buys the token, then burns it, after Echo confirmation completes.

#### `bridge`

```
@rake_agent bridge 0.05 ETH to robinhood
```

Brings ETH from outside into Robinhood after Echo confirmation completes.

### Echo confirmation

Echo protects asset-moving actions:

* `tip`
* `swap`
* `buy`
* `burn`
* `buyback`
* `bridge`

```
RAKE creates a draft
  -> user replies with the exact same amount
  -> exact match confirms
  -> mismatch cancels
```

The confirmation window is 180 seconds. Echo helps prevent execution caused by misclicks, typos, or prompt injection.

The LLM conversation layer cannot bypass Echo. It cannot guess missing amounts or generate executable calldata. The parser and schema control execution.

### Unsupported actions

RAKE does not support:

* Sending to raw `0x` addresses
* Creating LPs
* Sniping
* Placing limit orders
* Withdrawing to a CEX
* Bridging out of Robinhood


---

# 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/commands-and-assets/commands.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.