> For the complete documentation index, see [llms.txt](https://docs.ees.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ees.xyz/concepts/execution-fees.md).

# Execution fees

Fees are necessary to incentivise executors to execute jobs. We can largely view the fee as doing three things:

1. Compensating the executor paying gas fee to perform the on-chain transaction.
2. Incentivizing the executor beyond gas fee compensation, making it profitable to execute a job. Being an executor typically requires some kind of hardware and time invested and it should be worth the trouble economically.
3. Funding protocol development. Part of the fee goes to the protocol treasury, funding building of tools, integrations and protocol R\&D.

The total fee is calculated by the [fee module](/concepts/fee-modules.md) of the job and can be paid in any ERC-20 token. Getting the fee right is important as the job might not get executed if it is too low and the user risks overpaying if it is set too high. Fee modules contain mechanisms assisting in this. 

{% hint style="info" %}
**Note:** The execution fee is *always* paid by the sponsor. If no sponsor was set duing creation of a job, then the creator (`msg.sender`) will be set as sponsor.
{% endhint %}

{% hint style="warning" %}
**Warning:** Even though the fee can be paid in any ERC-20 token, it is the executors who decide if the job is worth executing. They might do that by looking at the current price of the fee token. To ensure reliable execution it is adviced to choose an established token with multiple price feeds.
{% endhint %}


---

# 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.ees.xyz/concepts/execution-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.