> For the complete documentation index, see [llms.txt](https://docs.saga.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.saga.xyz/saga-web-app/account-management/view-escrow-account-information.md).
# View Escrow Account Information
You can use the **Saga Web App** to view escrow related information, in addition to other functions.
To view escrow account balances, you can simply click the `Chainlet` tab on the landing page.
The last column in the image above displays the escrow account balance associated with each chainlet. You can also notice some chainlets having a `0 PSAGA` balance. Such chainlets have run out of funds and have been stopped.
You can also view detailed information associated to a chainlet's escrow account. Simply click on a chainlet to bring up its details.
In the example displayed above, we have selected a chainlet called `anewchain`. You can see it's escrow account balance and also view the funders of this chainlet under the `Funders` section.
{% hint style="info" %}
Anyone with a sufficient balance can contribute funds towards a chainlet. These funds are added to the chainlet's escrow account.
{% endhint %}
In the example above, this chainlet has two funding accounts, and they are listed under the `Funders` section, along with their respective stakes (%).
---
# 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.saga.xyz/saga-web-app/account-management/view-escrow-account-information.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.
