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

# Wallet Safety

Wallet safety is the user’s responsibility.

Zerax AI will never ask for your seed phrase, private key or recovery phrase.

{% hint style="danger" %}
Anyone asking for your seed phrase or private key is trying to steal your wallet.
{% endhint %}

***

### Never Share

Do not share:

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

***

### Safe Wallet Habits

Before confirming a transaction:

* Check the website URL
* Check the connected wallet
* Check the network
* Read the wallet confirmation
* Confirm only if the details are correct

***

### Common Scam Signs

Be careful of:

* Fake support accounts
* Private messages offering help
* Fake airdrops
* Fake token import links
* Unknown contract addresses
* Requests for wallet recovery phrases

***

### Summary

Your wallet keys should always stay private.

Zerax AI does not need your private key to help you use the platform.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.zeraxai.com/security/wallet-safety.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.