> For the complete documentation index, see [llms.txt](https://docs.hatchr.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hatchr.fun/getting-started/claim-creator-fees.md).

# Claim Creator Fees

Creators currently receive **40% of fees collected from their token's locked Uniswap V3 position**.

## Claim in Hatchr

1. Connect the wallet registered as the token's creator fee wallet.
2. Open the token page.
3. Select **Claim Fees**.
4. Review the claimable WETH and token amounts.
5. Submit the claim transaction.
6. Review the confirmation and explorer transaction.

The claim button is shown only when the connected wallet matches the registered creator wallet.

## Permissionless collection

The locker function itself is permissionless to call. This does not let a caller steal or redirect fees. Collected proceeds are transferred only to the creator and platform wallets registered for that position.

{% hint style="info" %}
Fees can accrue in WETH and in the launched token, depending on pool activity and token ordering. Claimable values are not guaranteed to be WETH-only.
{% endhint %}

See [Creator Fees](/protocol/creator-fees.md) for the contract-level mechanics.


---

# 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.hatchr.fun/getting-started/claim-creator-fees.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.