> For the complete documentation index, see [llms.txt](https://help.rabbithole.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rabbithole.gg/quest-protocol/introduction-to-quest-protocol.md). # Introduction to Quest Protocol Quest Protocol is the permissionless infrastructure to seamlessly connect onchain participants with onchain actions and foster sustainable network growth. Our user-friendly applications like Quest Terminal and RabbitHole make it easy to create onchain actions known as quests and reward participation. At the heart of the ecosystem are Protocol Rewards—the mechanism designed to incentivize all contributors, including the quest creator, participant and referrer. The equitable distribution of rewards encourages ongoing engagement, ultimately boosting protocol growth and crypto participation. **Key features of Quest Protocol include:** * **Permissionless access**: Any onchain individual or entity can deploy quests and distribute rewards. * **User-friendly interfaces**: Custom and intuitive interfaces to manage and interact with quests. * **Audience targeting**: Allowlists for quest creators to attract participants most aligned to their network’s goals. * **Real-time performance insights**: Real-time data to empower quest creators to measure, iterate and optimize quest strategies. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://help.rabbithole.gg/quest-protocol/introduction-to-quest-protocol.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 `build a script that syncs our docs to a CMS` 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.