> For the complete documentation index, see [llms.txt](https://docs.world.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.world.inc/essentials/leverage.md).

# Leverage

## Is leverage the same as available margin?

Often in crypto, "leverage" is used in the context of a single perp position. World is different in that it looks at portfolio-level, instead of position-level risk. While [Available Margin & Collateral](https://docs.world.inc/essentials/available-margin-and-collateral.md) is not exactly the same as "leverage", these concepts are related in that they are different ways to measure and manage risk.

When you choose the size of your position, you are using your whole portfolio as collateral. Your leverage is not configured as a setting in the order panel. Instead, it is implied by the size of your positions. Your max leverage available in any single position is also determined by your whole portfolio.

## Portfolio Leverage

Leverage can be calculated as the total size of your positions divided by your total balance (the sum of the USDT value of your spot assets).

On World, users can safely take higher amounts of leverage for hedged portfolios, enabled by [ATLAS - World's Risk Engine](https://docs.world.inc/tl-dr-unique-features/atlas.md).

This metric is a helpful heuristic to some traders; it is not used in any calculations and does not trigger liquidation.


---

# 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.world.inc/essentials/leverage.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.
