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

# Balances

Review balances returned by the active trading account

<figure><img src="https://1571380119-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfwUo1o7rINODRyyILQE1%2Fuploads%2FvhQ0378tdGkwdWRQNUdD%2Fimage.png?alt=media&amp;token=690e17c2-f8b9-4dbe-8e7e-c6c22ca6313c" alt="Balances table showing spot and perps balances associated with the account."><figcaption><p>Balances table showing spot and perps balances associated with the account.</p></figcaption></figure>

Balances shows the spot and derivatives balances returned by your active trading account. The columns and labels can differ by exchange.

Use this block to confirm which assets are available, which balances are being used as margin, and whether your account has enough collateral before opening new positions.

## When to check Balances

* Before placing a trade from the [Trade form](/terminal-sections/trade-form.md).
* After deposits, withdrawals, or transfers.
* When available margin in the [Account](/terminal-sections/account.md) block does not match what you expected.
* Before switching strategies that require more collateral.

Use **Hide dust** in the Balances panel when you want to remove very small balances from the list. The filter changes the display only; it does not move or convert funds.

Related pages: [Account](/terminal-sections/account.md), [Positions](/terminal-sections/positions.md), and [Trading accounts](/getting-started/trading-accounts.md).


---

# 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.proliquid.xyz/terminal-sections/balances.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.