> For the complete documentation index, see [llms.txt](https://docs.enzyme.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enzyme.finance/onyx-user-documentation/enzyme-vault/fees/hurdle-rate.md).

# Hurdle Rate

## What the hurdle rate does

A hurdle rate defines a minimum level of performance that must be achieved before any performance-based compensation becomes payable. If performance does not exceed this threshold, the effective performance fee is zero, regardless of the nominal fee rate.

\
Put differently:

* The hurdle rate does not cap returns
* It does not introduce a separate fee
* It conditions the existence of a performance fee on achieving a minimum level of performance
* The hurdle rate therefore acts as a gatekeeper, not as an additional fee layer.

## How does it operate

Conceptually, the mechanism works as follows:

\
1\. Performance is measured over the relevant period (commonly relative to a high-water mark).\
2\. Performance is compared against the hurdle rate.\
3\. If performance ≤ hurdle rate → No performance fee is payable.\
4\. If performance > hurdle rate → A performance fee is calculated on the excess performance according to the defined fee rules.<br>

The hurdle rate is applied within the performance fee calculation itself, not as a post-processing adjustment.

## Relationship to performance fees

Key characteristics:

* The hurdle rate is embedded within performance fee logic
* It can reduce the effective performance fee down to zero
* It is not a standalone or composable mechanism
* It cannot be meaningfully layered with additional hurdle constructs

<br>


---

# 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.enzyme.finance/onyx-user-documentation/enzyme-vault/fees/hurdle-rate.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.
