> 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/dashboard/wallet-profile.md).

# Wallet Profile

The Wallet Profile section helps users manage the wallet address connected to their Zerax AI account.

This wallet may be used for rewards, claims, staking and account-related token activity.

{% hint style="warning" %}
Always check your wallet address carefully before saving it.
{% endhint %}

***

### Why Wallet Profile Matters

Your wallet address may be used for:

* Reward claim payouts
* Staking activity
* Token-related account records
* Presale-related tracking
* Future platform access

***

### Adding a Wallet Address

Users should add a wallet address that they control.

Before saving, make sure:

* The address is correct
* You control the wallet
* The wallet supports the required network
* You did not copy an incorrect address

***

### Updating Your Wallet

If you need to change your wallet address, update it from the profile area.

After changing your wallet, always check that the new address is saved correctly.

{% hint style="danger" %}
Do not use an exchange deposit address for reward claims unless the platform specifically supports it.
{% endhint %}

***

### Wallet Safety

Never share:

* Seed phrase
* Private key
* Recovery phrase
* Wallet password
* Verification codes

Zerax AI will never ask for your private wallet keys.

***

### Summary

The Wallet Profile section helps users manage the wallet address connected to their account.

A correct wallet address is important for rewards, staking and future token-related 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/dashboard/wallet-profile.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.