> For the complete documentation index, see [llms.txt](https://docs.tradoor.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradoor.io/tradoor-user-guide-v2/how-to-trade-on-tradoor/trading-perps-101/how-to-navigate-tradoors-perps-trading-page/what-does-long-short-rate-mean.md).

# What does "Long/Short Rate" mean?

## **(E) Long/Short Rate**

<div align="left"><figure><img src="/files/tFOxmPZ7hTPzEM43wJFb" alt="" width="135"><figcaption></figcaption></figure></div>

This represents **the proportion of traders holding long positions compared to those holding short positions**. It’s a key metric for assessing market sentiment and potential price movements. This is what it means:

* **High Long/Short Rate:** This often indicates bullish sentiment, suggesting that many traders expect prices to rise. However, if the ratio is extremely high, it may signal overconfidence, which can lead to a price correction.
* **Low Long/Short Rate:** Conversely, a low ratio suggests bearish sentiment, with more traders betting on price declines. An extremely low ratio might indicate that the market is oversold and could be due for a rebound.

**The Long/Short Rate can aid in the following:**

**Market Dynamics:** The Long/Short Ratio can help traders gauge potential price movements. If the majority are long and prices start to decline, there could be a wave of liquidations, pushing prices down further.

**Risk Management:** Traders use the Long/Short Ratio as part of their risk management strategy, helping them to make more informed decisions based on the overall market positioning


---

# 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.tradoor.io/tradoor-user-guide-v2/how-to-trade-on-tradoor/trading-perps-101/how-to-navigate-tradoors-perps-trading-page/what-does-long-short-rate-mean.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.
