> For the complete documentation index, see [llms.txt](https://docs.lighter.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lighter.xyz/trading/unified-trading-accounts.md).

# Unified Trading Accounts

You can enable UTA from the web app or through the API. See [Manage Trading Mode and Margin](https://docs.lighter.xyz/developers/integration-guides/manage-trading-mode-and-margin).

<figure><img src="https://855888483-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHkh5jOwCd7orp1uLEdzQ%2Fuploads%2Fh3UHMNaBemXbS2Yr2IZo%2F02-unified-trading-accounts.png?alt=media&amp;token=096d0d7e-00de-4e6f-bdb1-4aab27f497e5" alt=""><figcaption></figcaption></figure>

#### Unified Trading Account (UTA)

Unified Trading Accounts (UTA) enable unified margin across spot and perpetual USDC balances, including [Multi-Asset Margin](/trading/multi-asset-margin.md), which supports eligible spot assets as collateral in perpetual markets.

#### Simple Trading Account

In Simple Trading Accounts, perpetual and spot balances are maintained separately. Perpetual positions may only use settlement assets as collateral. Cross-margining applies exclusively within perpetual markets and does not extend to spot balances.


---

# 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.lighter.xyz/trading/unified-trading-accounts.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.