> 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/how-rake-works/harvest.md).

# Harvest

Permissionless collection of accumulated fees into RakeVault for source-defined distribution.

## Permissionless fee collection

Harvest moves accumulated fees into RakeVault. It connects a launched token's fee sources to the distribution and buy-burn process.

```
@rake_agent harvest $TICKER
```

### Harvest path

```
Curve + Hook + Escrow
    ↓
RakeVault
    ↓
Automatic fee split
    ↓
Automatic buy-burn
```

The harvest process pulls accumulated fees from the curve, hook, and escrow. It routes those fees into RakeVault.

RakeVault then applies the source-defined distribution. That distribution sends the creator allocation and initiates the $RAKE and $PONS market-buy burn allocations. See [Fee Split](/rake/how-rake-works/fee-split.md) for the allocation details.

### Who can harvest

Harvest is permissionless. Any actor can trigger it.

This includes:

* The token creator
* The RAKE team
* Any other actor

Harvest does not require waiting for an administrator or gatekeeper. This allows accumulated fees to progress into RakeVault without limiting the trigger to one role.

{% hint style="info" %}
Permissionless access means any actor can initiate harvest. It does not require creator, team, or administrator status.
{% endhint %}

### Keeper harvest

A keeper also runs in the background. The keeper can trigger harvest automatically when accumulated fees are worthwhile and gas is cheap.

The keeper is an automated trigger, not a separate distribution path. It uses the same harvest route into RakeVault.

| Trigger model          | Who initiates it  | When it can occur                                     |
| ---------------------- | ----------------- | ----------------------------------------------------- |
| Permissionless harvest | Any actor         | When that actor chooses to trigger harvest            |
| Keeper harvest         | Background keeper | When accumulated fees are worthwhile and gas is cheap |

The stated keeper conditions do not define a guaranteed harvest time. They define when the background keeper can trigger the process.


---

# 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/how-rake-works/harvest.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.