> For the complete documentation index, see [llms.txt](https://docs.brava.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brava.finance/platform/ask-brava.md). # Ask Brava Ask questions about the workspace you can access. ## Ask Brava The assistant inside the app. It knows your workspace. ### What to ask it Ask about your positions, activity, a pool you are considering, or a number on screen. It reads what you can read: the workspace you are in and nothing beyond it. ### What it does not do Ask Brava does not move capital. It answers, explains, and points to the record. You take actions in the relevant panel, with transaction details in front of you. Answering a question and instructing a transaction are different acts. Brava keeps them apart. ### Ask Brava and agents They are not the same thing. **Ask Brava** answers questions inside the app. **An agent** works through Brava on your behalf. It researches and prepares transactions that wait for your approval on Portfolio. One is a conversation. The other is a proposal. --- # 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.brava.finance/platform/ask-brava.md?ask=&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.