> 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/when-to-use-arbital.md).

# Who Should Use Arbital?

Arbital is built for:

**Everyday traders** - you want to buy crypto, stocks, or perps without juggling multiple apps, wallets, and signups. One account, every market.

**Degens and narrative traders** - you live on the timeline. Arbital's social feed puts sentiment on every ticker so you can go from spotting a narrative to holding a position in one click.

**Passive earners** - you don't want to actively trade. Deploy a market making strategy on your own perp DEX account, set a budget, and let it run - your bot's activity earns from exchange incentive programs while it works. Grid strategies are rolling out.

If you can use a trading app, you can use Arbital. No quant background required.


---

# 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/when-to-use-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.