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

# Trading on Arbital

The Arbital terminal puts every market in one screen.

## Markets and social

Browse assets in the Market tab, or switch to the Social tab to see a live feed of what traders are posting - with bullish or bearish sentiment tagged on every mentioned ticker. Spot a narrative, click the ticker, and you are on the chart.

## Charts and data

Every asset gets a live chart with multiple timeframes, from one second to daily, plus the numbers that matter: price, market cap, 24h volume, liquidity, and fully diluted value.

## Buying and selling

Pick an asset, enter an amount (or use the quick amount buttons), and execute. Your balances, open positions, orders, and trade history live in tabs right under the chart - no separate portfolio page needed.

## Non-custodial by design

You trade from your own wallet. Arbital checks your balance securely when execution starts and never takes custody of your funds.


---

# 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://arbital-1.gitbook.io/docs/trading/trading-on-arbital.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.