> 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/reward-claims.md).

# Reward Claims

Users can claim earned ZXAI rewards when they reach the minimum claim requirement.

Reward claims may go through review before completion.

***

### Claimable Balance

The dashboard may show a claimable ZXAI balance from:

* Completed quests
* Daily quests
* Daily streaks
* Referral rewards
* Approved campaigns

***

### Claim Process

1. Complete valid tasks.
2. Earn ZXAI rewards.
3. Reach the minimum claim amount.
4. Submit a claim request.
5. Wait for review.
6. Track the status in the dashboard.

***

### Claim Statuses

| Status        | Meaning                                      |
| ------------- | -------------------------------------------- |
| **Pending**   | Claim is waiting for review.                 |
| **Completed** | Claim was approved.                          |
| **Rejected**  | Claim was rejected or could not be verified. |

{% hint style="info" %}
Rejected claim amounts may return to the claimable balance depending on system rules.
{% endhint %}

***

### Wallet Requirement

Users should add a valid wallet address before claiming rewards.

{% hint style="warning" %}
A wrong wallet address may delay or prevent reward payout.
{% endhint %}

***

### Summary

Reward Claims allow users to request payout of earned ZXAI rewards after completing valid activity.


---

# 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/reward-claims.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.
