> 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/trading-and-utility/buy.md).

# Buy

RAKE's supported buy action and the source-defined path for execution.

## Buy

Buy purchases a token using ETH. The command explicitly states the ETH amount and the token.

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

```
Buy request
    ↓
Token and ETH amount specified
    ↓
Echo draft
    ↓
Exact confirmation
    ↓
Buy executes
```

Buy requires Echo confirmation. RAKE creates a draft from the requested token and ETH amount. The user confirms that exact amount before execution. [Echo Confirmation](/rake/how-rake-works/echo-confirmation.md) covers the complete confirmation flow.

### Buy and buyback

`buy` purchases a token.

`buyback` purchases a token using ETH, then burns the purchased token. [Burn & Buyback](/rake/trading-and-utility/burn-and-buyback.md) covers that combined action.


---

# 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/trading-and-utility/buy.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.