> For the complete documentation index, see [llms.txt](https://docs.zeraxai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeraxai.com/reward/daily-quests.md).

# Daily Quests

Daily Quests are repeatable or regularly updated tasks that encourage users to stay active in the Zerax AI ecosystem.

These quests may change based on campaigns, social activity, community goals or platform updates.

{% hint style="info" %}
Daily Quests may refresh daily or during specific campaign periods.
{% endhint %}

***

### What Are Daily Quests?

Daily Quests are tasks users can complete to earn extra ZXAI rewards and XP.

They may include social actions, content creation, comments, shares or community participation.

***

### Example Daily Quests

Daily Quests may include tasks such as:

| Quest Example                    | Description                                                              |
| -------------------------------- | ------------------------------------------------------------------------ |
| **Post on Binance Square**       | Share a post about Zerax AI and tag the project.                         |
| **Comment Under a Binance Post** | Leave a relevant comment and tag Zerax AI.                               |
| **Comment Under an X Post**      | Reply to selected posts with a meaningful comment.                       |
| **Create a YouTube Video**       | Publish a video explaining Zerax AI, its ecosystem or presale.           |
| **Create a Short Video**         | Make a short-form video for YouTube Shorts, TikTok or Instagram Reels.   |
| **Share a Zerax AI Update**      | Share official announcements with your audience.                         |
| **Write a Thread**               | Create an educational thread about Zerax AI, AI systems or Web3 utility. |
| **Invite Community Discussion**  | Start a relevant discussion about Zerax AI in supported platforms.       |

***

### Content-Based Tasks

Some Daily Quests may require users to create original content.

Examples:

* A YouTube video about Zerax AI
* A short-form video explaining ZXAI
* A Binance Square post
* An X thread
* A community post
* A visual or infographic
* A tutorial-style post

{% hint style="warning" %}
Low-quality, copied, spam or misleading content may not be accepted.
{% endhint %}

***

### What Makes a Daily Quest Valid?

A valid Daily Quest should usually be:

* Publicly visible
* Related to Zerax AI
* Not spam
* Not copied from another user
* Completed with the correct tag, link or instruction
* Submitted with the correct proof if required

***

### Daily Quest Rewards

Daily Quests may reward:

* ZXAI
* XP
* Level progress
* Streak-related activity
* Special campaign bonuses

***

### Summary

Daily Quests help active users earn extra rewards while supporting Zerax AI’s visibility and community growth.


---

# 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.zeraxai.com/reward/daily-quests.md?ask=<question>&goal=<user_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.
