> 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/archive/legacy-products/archived-pancakeswap-quest/rewards.md).
# Rewards
{% hint style="danger" %}
\[Archived] PancakeSwap Quest – As of 28th February 2025
{% endhint %}
For beta mode, quests are split into two types - **quests with rewards and without rewards**. For quests without rewards, users will complete the tasks in order to learn more about DeFi or specific products and campaigns, with no token rewards or points at the moment.
For quests with rewards, users can earn token rewards by completing them. The rewards will be distributed via a lucky draw to all users completing the quest, as shown below.
For example, if the total reward is 1000 USDT with 10 stipulated winners, 10 users will be drawn to receive the reward.
How to claim rewards:
1. To claim rewards at the end of the quest, check if you have won the quest via the quest page. Winners should see a “Claim reward” button below the prize amount.
2. Click “Claim Reward” and sign the transaction.
3. Check your wallet for the token reward.
---
# 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/archive/legacy-products/archived-pancakeswap-quest/rewards.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.
.png?alt=media&token=8179addc-a6df-4aca-a812-4bc4a27c8ed2)