> For the complete documentation index, see [llms.txt](https://ocelex.gitbook.io/ocelex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ocelex.gitbook.io/ocelex/protocol-overview/dex-functionalities/external-incentives.md).

# External Incentives

While partner projects typically provide external incentives (formerly “bribes”), they aren’t the only ones who can. Any user can create external incentives to encourage voting for pairs with active gauges. Ocelex also supports this by allocating a portion of oOCX redemptions and treasury funds to incentivize specific pools, fostering active participation and sustaining a vibrant ecosystem.

#### Incentives Methodology

For Ocelex’s external incentive methodology, we analyze gauge performance by assessing TVL efficiency and fee generation. Using an analytical sheet, the team manually places incentives to accurately reflect each gauge’s performance. In some cases, especially with partners, we engage in incentive-matching agreements to help kickstart new gauges, ensuring they attract attention and liquidity from the outset.

#### Claiming External Incentives

When an epoch flips, all rewards become instantly claimable. Simply visit the Rewards page, select the NFT used for voting, and claim your rewards.


---

# 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://ocelex.gitbook.io/ocelex/protocol-overview/dex-functionalities/external-incentives.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.