> For the complete documentation index, see [llms.txt](https://docs.claimr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.claimr.io/quests.md).
# Quests
Quests transform your marketing goals into interactive journeys. Guide your audience through engaging experiences that make them want to explore your brand, products, and services.
#### What you can do with Claimr quests?
**Turn goals into games**: Convert your marketing objectives into exciting challenges. Make every interaction fun and rewarding, keeping users engaged from start to finish.
**Guide users to take action**: Direct participants through specific activities aligned with your goals—whether you're building brand awareness, driving traffic, or boosting social engagement.
**Understand your audience**: Track how users move through your quests and what they respond to. Gain insights into their preferences, interests, and behavior patterns.
**Reward participation**: Offer compelling incentives that match your audience's interests: NFTs, tokens, exclusive access, discounts, or custom rewards that keep users coming back.
**Build community**: Create shared experiences that bring your audience together. Foster a sense of belonging as users complete quests alongside others who share their interests.
---
# 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.claimr.io/quests.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.