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

# Fees

The Ocean Enterprise Collective defines various fees for creating a sustainability loop.

One transaction may have fees going to several entities, such as the marketplace operator where the asset was published, the Ocean Node provider, and the Ocean Enterprise Collective e.V.

* **Marketplace**: the marketplace where the asset is published or consumed
* **Provider**: the Ocean Node facilitating asset consumption. May serve up data, run C2D jobs, etc.
* **Ocean Enterprise Collective**: for developing and maintaining the OE code base

<table><thead><tr><th width="239.5">Fee Type</th><th align="center">Value</th></tr></thead><tbody><tr><td>Marketplace</td><td align="center">set by the marketplace operator <br>for asset publishing and/or consumption</td></tr><tr><td>Provider</td><td align="center">set by the Ocean Node operator</td></tr><tr><td>Ocean Enterprise Collective </td><td align="center">set by OEC eV at 1.9% of the asset and compute job price<br>with a minimum value of 1 cent</td></tr></tbody></table>

{% hint style="info" %}
Stay up-to-date with the latest information! The values within the system are regularly updated. We recommend verifying the most recent values directly from the [contracts](https://github.com/oceanprotocol/contracts) and the [market](https://github.com/oceanprotocol/market).
{% 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 by asking a question.

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

```
GET https://docs.oceanenterprise.io/developers/fees.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.
