> For the complete documentation index, see [llms.txt](https://docs.usd.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usd.ai/app-guide/depositor/dashboards.md). # Dashboards ### Total Value Locked > * Cumulative TVL over time > * TVL is calculated as all stablecoin backing USDai and sUSDai plus all income generated ### Staking APY > * The current and historical yield of staking USDai > * sUSDai Staking Ratio = the % of USDai that is currently being staked ### Proof of Reserves > * A summary view all of the underlying collateral reserves and loans powering sUSDai yield ### Key Ratios > * USDai Reserve Ratio: The % of USDai that is backed by stablecoins (instantly redeemable). > * USDai Staking Ratio: The % of USDai that is currently being staked > * sUSDai Utilization: The % of sUSDai liquidity that is currently deployed to loans along with the expected change in Utilization assuming all Upcoming loans are funded --- # 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.usd.ai/app-guide/depositor/dashboards.md?ask=&goal= ``` `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.