> For the complete documentation index, see [llms.txt](https://docs.elevateelysium.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elevateelysium.xyz/reference/faq.md).

# FAQ

**Can I withdraw from my agent's wallet?** No. It is locked by design. Only the agent spends, within limits.

**What if my AI key runs out?** The agent sleeps and tells you why. Add credit or switch to mind credits.

**Can the agent lose all its money?** Each move is capped (10% on chain, 5% by default on the server) and daily at 30%, but repeated moves can still lose value. Use the limits.

**Is the chart real-time?** It is built from indexed trades and refreshes every few seconds on short intervals.

**Can I change the model or powers later?** Yes, on the agent page.

**Does the live view show a real screen?** It shows real commands, output and results, not video.


---

# 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.elevateelysium.xyz/reference/faq.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.