# Introduction Vote incentives proved to be one of the most sustainable yield sources in DeFi. With the advent of ve(3,3) DEXs it is gaining even more popularity. Given the volumes that are going through ve-model protocols, there is a suprising lack of neutral data sources where users can browse through in order to take better informed investment decision. VoteX aims to fill this void by aggregating vote incentives offered by various protocols. Mechanism behind vote incentives are complex and we believe it is important to display easy to digest data around them. There are many protocols adopting ve-model into their tokenomics and increasingly more complex products getting built each day. We hope to contribute to this space by creating a platform where users can access all veProtocols under a single roof. VoteX has the potential to evolve into multiple different directions. Given the complex nature of vote incentives our first contribution will be to provide accurate data for the community. This means there is no token or airdrop (YET!). Whichever direction we take, we will stick to our core values. ### Core Values **Community Oriented** Our aim is to provide the community with a much required tool to analyze best performing vote incentives accross DeFi **Neutrality** All of our data is standardized and display an accurate comparision between various integrated platforms. We don't favour any platform over the other and objectively visualize the opportunities and risk present **Flexibility** In a market that evolves at light speed, you can't afford to stay rigid. VoteX will always be on the look out for new protocols and products that are built on top of vote incentives and will position itself accordingly --- # Agent Instructions: 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: ``` GET https://docs.votex.fi/overview/introduction.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.