> For the complete documentation index, see [llms.txt](https://docs.pancakeswap.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pancakeswap.finance/welcome-to-pancakeswap/vecake-sunset/bribes-vote-incentives.md).
# Bribes (Vote Incentives)
Apart from earning CAKE via our weekly [CAKE reward pools](/welcome-to-pancakeswap/vecake-sunset/archive-vecake/earn-cake-weekly.md), veCAKE holders can vote for gauges to claim bribes from external bribe marketplaces. These bribes are usually submitted by external project teams on some of our [veCAKE Managers](/welcome-to-pancakeswap/vecake-sunset/archive-vecake/vecake-managers.md).
This serves as an additional source of yield for veCAKE holders, and also diversifies the type of tokens they receive as yield.
There are two types of bribe marketplaces:
1. Primary bribe marketplaces allow projects to submit bribes to reward **veCAKE holders** for voting for their desired gauges.
2. Secondary bribe marketplaces allow projects to submit bribes to reward a **derivative project's token holders** (e.g vlCKP from Cakepie) for voting for their desired gauges. The protocol in question (e.g. Cakepie) will then vote for the gauges with their own veCAKE holdings, based on the vote outcome of their token holders.
We currently have two primary bribe marketplaces where veCAKE holders can vote for gauges and claim bribes from external teams:
1. [Hidden Hand](https://hiddenhand.finance/pancakeswap)
2. [Votemarket (by StakeDAO)](https://votemarket.stakedao.org/?market=cake\&solution=All)
veCAKE holders should visit these bribe marketplaces regularly and vote for gauges that can help optimize their yield on veCAKE.
---
# 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.pancakeswap.finance/welcome-to-pancakeswap/vecake-sunset/bribes-vote-incentives.md?ask=&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.
