> 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/automated-strategies/strategies.md).

# Strategies

Market making is available now. Grid trading is rolling out.

## TWAP Market Making

Arbital's market making bots run a TWAP-based passive strategy.

TWAP (Time-Weighted Average Price) means orders are placed gradually over time, rather than all at once.

But unlike traditional TWAP (used for execution), Arbital's TWAP is designed for market making, not directional trading.

## What the Bot Actually Does

At all times, the bot:

* Places limit buy orders slightly below market price
* Places limit sell orders slightly above market price
* Refreshes these orders every few seconds

So it:

* Buys low
* Sells high
* Repeats this many times

This creates:

* Trading volume
* Spread capture


---

# 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/automated-strategies/strategies.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.