> For the complete documentation index, see [llms.txt](https://programmable.market/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://programmable.market/docs/launch/economics/earnings.md).

# Creator earnings

A creator fee is part of a coin's trading rules. It accrues to the recipients recorded for that coin and stays in the fee contract until claimed. The launching wallet is not necessarily the recipient.

## Module Mode

Choose the creator rate before launch. If selected modules receive a share of that fee, your earnings are the remainder. Fees accrue in the asset paired with the coin; an ETH-funded launch can use WETH for fee accounting.

The platform fee is separate. [Fees and revenue](/docs/launch/economics.md#module-mode) shows the rates and an example. A creator rate of 0% produces no creator earnings from those trades.

## Claiming fees

Connect the wallet recorded as the recipient and use the claim controls supported by the coin's fee contract. Custom projects define their own claim interface. An API key cannot claim funds.

A claim withdraws fees already earned. Analytics may include those balances before you claim them; withdrawing them does not add revenue a second time. Confirm the asset and recipient before signing.

Earlier coins keep their original fee and recipient rules. The [fee reference](/docs/developers/machine-readable/fee-versions.md) covers those versions.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://programmable.market/docs/launch/economics/earnings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.