> For the complete documentation index, see [llms.txt](https://docs.cookie.community/cookie-dao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cookie.community/cookie-dao/~/revisions/Fco0iu68s1BCbw8w3zbi/cookie.fun/cookie-snaps/how-to-claim-rewards.md).
# How to claim rewards
To be eligible for rewards, you have to connect your rewards wallet on [cookie.fun](http://cookie.fun/) before each campaign’s snapshot. To do that, go to cookie.fun and to your profile in the top right corner, and click on the tab “Wallets”.
**Each project running a campaign with Cookie decides whether they want to distribute the rewards via the Cookie Claim portal, built in partnership with Sign, or on their own – via their infra or direct airdrop i.e.** Details regarding upcoming distributions can be found on our socials and on [cookie.fun/campaigns](http://cookie.fun/campaigns).
**How the Cookie Claim Portal works:**
1. Before the distribution date all rewards are loaded onto a smart contract (including the vested tokens).
2. The claim goes live according to the agreed and announced schedule.
3. To claim your rewards, you need to log in to the rewards portal with your Cookie Snaps rewards wallet.
Go here to access the Cookie Claim Portal: Cookie Claim Portal
---
# 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://docs.cookie.community/cookie-dao/~/revisions/Fco0iu68s1BCbw8w3zbi/cookie.fun/cookie-snaps/how-to-claim-rewards.md?ask=&goal=
```
`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.