> 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/security/user-responsibility.md).

# User Responsibility

Users are responsible for checking all details before making payments, submitting claims or interacting with smart contracts.

Crypto transactions cannot usually be reversed.

***

### User Checklist

Before confirming any action, check:

* Official website
* Correct network
* Correct wallet address
* Correct payment amount
* Correct transaction hash
* Gas fees
* Wallet confirmation details

***

### Manual Pay Responsibility

For Manual Pay, users must submit accurate information.

Incorrect details may cause delays or rejection.

| Detail      | User Responsibility                            |
| ----------- | ---------------------------------------------- |
| **Amount**  | Send the correct amount.                       |
| **Network** | Use the correct network.                       |
| **TXID**    | Submit the correct transaction hash.           |
| **Wallet**  | Provide the correct sender wallet if required. |

***

### Reward Responsibility

Users should complete quests honestly.

Fake activity, copied content or spam may be rejected.

{% hint style="danger" %}
Do not try to manipulate rewards, referrals or payment records.
{% endhint %}

***

### Summary

Zerax AI provides the platform, but users must act carefully.

Always verify before confirming any transaction or submission.


---

# 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/security/user-responsibility.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.
