> For the complete documentation index, see [llms.txt](https://remittix-organization.gitbook.io/remittix-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://remittix-organization.gitbook.io/remittix-whitepaper/30.10-remittix-markets-risk.md).

# 30.10 Remittix Markets Risk

Perpetual futures and leveraged trading involve a high degree of financial risk.

Leverage allows a user to control a position larger than the collateral committed to it. This can increase potential gains, but it can also increase losses.

An adverse market movement may result in partial or complete loss of the collateral assigned to a position. Positions may also be liquidated automatically where margin falls below the requirements of the underlying trading infrastructure.

Funding rates, market liquidity, and rapid price movements can further affect the result of a trade.

{% hint style="warning" %}
Remittix Markets is intended for users who understand the operation and risks of perpetual futures. Availability may also be restricted according to jurisdiction.
{% endhint %}


---

# 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://remittix-organization.gitbook.io/remittix-whitepaper/30.10-remittix-markets-risk.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.