> For the complete documentation index, see [llms.txt](https://v1risk.infinity.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://v1risk.infinity.exchange/the-infinity-protocol/transparency-reports.md).

# Transparency Reports

With a complex risk management system and a wide variety of collateral assets, it's incumbent upon us to share exactly how these risk are managed and to what extent Infinity itself has risks, be they directional, liquidity, correlation, volatility or other risk types. 

We've built a simulation tool that looks at first-order, and second-order effects of a market meltdown. These analyses are run on a real-time basis for our internal risk managment purposes, and will be made available to the broader public. 

Please see [infinity.exchange/risk/](https://infinity.exchange/risk/) for our current analyses (available soon!)

We look to build on these over time. 


---

# 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://v1risk.infinity.exchange/the-infinity-protocol/transparency-reports.md?ask=<question>&goal=<endgoal>
```

`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.