> 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-streak.md).

# Daily Streak

Daily Streak rewards users for returning and staying active consistently.

A streak may increase when a user visits or interacts with the dashboard on consecutive days.

{% hint style="info" %}
Daily Streak is different from Daily Quests.\
Daily Streak rewards consistency, while Daily Quests reward specific tasks.
{% endhint %}

***

### How Daily Streak Works

| Day           | Result                                          |
| ------------- | ----------------------------------------------- |
| **Day 1**     | Streak starts.                                  |
| **Day 2**     | Streak continues.                               |
| **Day 3**     | More progress is unlocked.                      |
| **Next Days** | Rewards may increase depending on system rules. |

***

### Streak Rewards

Daily Streak may provide:

* ZXAI rewards
* XP
* Activity bonuses
* Campaign bonuses

***

### Missing a Day

If a user misses a day, the streak may reset or stop progressing depending on the active rules.

{% hint style="warning" %}
Daily Streak rewards may depend on real dashboard activity and system verification.
{% endhint %}

***

### Summary

Daily Streak is designed to reward consistent activity and help users stay connected to the Zerax AI ecosystem.


---

# 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-streak.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.
