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

# Grid Bots

A grid bot places a ladder of limit orders across a price range you define: buys below the current price, sells above it. When price drops it fills your buys; when it climbs back it fills your sells, and every down-up crossing captures the gap between two levels. Grid bots live at **Bots** (`/bots`). DCA and TWAP bots are listed there as *Soon*; for a time-sliced order use the [TWAP order type](https://dasus.gitbook.io/dasus-docs/trading/twap.md) in the terminal.

Grid orders are real limit orders on Hyperliquid, placed with your session key. They stay on the book until they fill or you cancel them — with the page closed too.

{% hint style="warning" %}
**Levels are not replenished.** The bot places the ladder once. When a level fills it stays empty — nothing re-places a sell above a filled buy. To rebuild the ladder, create the grid again. This differs from the "infinite" grid bots of centralised exchanges.
{% endhint %}

## Setting up a grid

| Setting                | What it controls                                                                                                                                    |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Perps / Spot**       | Perp markets trade with leverage and carry a range stop; spot grids hold the token                                                                  |
| **Direction**          | **Neutral** — buys below and sells above the price. **Buy grid** — only buys (accumulate on dips). **Sell grid** — only sells (distribute on pumps) |
| **Pair**               | Any market from the full selector — crypto perps, HIP-3 perps and spot pairs                                                                        |
| **Investment**         | In USDC or in the coin. It is split equally across the orders that will actually be placed                                                          |
| **Price range**        | Lower and upper price. Presets ±5%, ±10% and ±20% around the current price, or **30D range** — the real low and high of the last 30 days            |
| **Grids**              | 2 to 30 levels, evenly spaced                                                                                                                       |
| **Leverage** (perps)   | The terminal's leverage popup, in cross margin; **Confirm** signs it on Hyperliquid at once                                                         |
| **Range stop** (perps) | 3%, 5% or 10% beyond the range — see below                                                                                                          |

Levels within 0.05% of the current price are skipped, so no order fills the moment it is placed. In a Neutral grid the current price must be inside the range; a Buy or Sell grid may sit entirely on one side of it.

The preview draws the ladder over the last 30 days of price — you see at a glance whether the range makes sense — and lists the exact **Orders to place** (side, price, size) before you create anything.

## What the preview tells you

| Row                                                          | Meaning                                                                                                                                                                            |
| ------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Profit / grid**                                            | The spacing between two levels as a % of price, gross and **net** of a full round trip: the Dasus bots fee twice plus Hyperliquid's maker fee twice (grid orders rest on the book) |
| **Orders**                                                   | How many buys and sells will be placed                                                                                                                                             |
| **Per order**                                                | Investment ÷ orders. Must be at least **$10**: *Each order must be at least 10 USDC. Increase investment or reduce levels.*                                                        |
| **Liquidation price (approx.)**                              | For a leveraged grid, an approximate liquidation price for the full position the grid would hold if price trends through one side. *No liquidation (1x)* at 1×                     |
| **If price reaches …**                                       | One sentence: at the edge of the range you would be long (or short) with this size and this unrealized loss, and liquidation at that price                                         |
| **Available / Order value / Margin required / Platform fee** | The account check. The platform fee shown is the **bots** rate — the one these orders are actually charged                                                                         |

## Range stop (perps)

Every perp grid carries a **range stop**: a stop-loss attached to each entry order on the side that accumulates in a trend (the buys of a neutral or buy grid, the sells of a sell grid), placed 3%, 5% or 10% beyond the range. It goes out with the entry as a Hyperliquid trigger order, so it fires with the page closed. In the page's words: *If price leaves the range by that %, the bot's position is closed. The stop is attached to each order and lives on the protocol: it fires even with the page closed.* With leverage above 1× the stop is marked as required.

Spot grids have no stop: there is no leverage, and the downside is holding the token.

## Creating and stopping a grid

1. Connect and, the first time, **Enable trading** (session key plus the platform-fee approval).
2. Set the grid and read the warnings: an open position on the pair (*the grid's orders can increase or reduce it*), existing open orders on the pair (*they will mix with the new grid*), the price outside a neutral range, an order below $10, not enough balance, or — on spot — not enough of the token for the sell side (*On spot, selling requires holding the token*).
3. **Create Grid bot**. The orders are placed one after another; the toast reports *N orders placed* or *ok placed · fail failed*.

**Active grid · COIN** lists the open limit orders on that pair — all of them, including any you placed by hand — with **Cancel all**. Cancelling removes the resting orders; a position the grid already opened stays yours to manage from the Positions tab, including its [TP/SL](https://dasus.gitbook.io/dasus-docs/trading/tp-sl.md). The same orders appear in **Open Orders** in the terminal.

## Guardian Mode

[Guardian Mode](https://dasus.gitbook.io/dasus-docs/trading/guardian-mode.md) applies to grids too. If your leverage limit is below the grid's leverage the bot does not start (*Guardian blocks this bot: your limit is Nx and you're asking for Mx*), and each order is checked against your rules as it is placed.

## When grids do well — and when they don't

**Grids do best in a range.** While price oscillates inside your range the ladder buys dips and sells rallies, one round trip per pair of levels.

**Grids do badly in a trend.** If price leaves the range:

* **Above it** — every sell level has filled; the grid holds no more inventory to sell and simply stops earning while price runs.
* **Below it** — every buy level has filled and you hold the full buy side with an unrealized loss. On perps the range stop closes it beyond the stop level; on spot you keep the tokens.

{% hint style="danger" %}
*Grid trading involves risk. With leverage, if the price leaves your range your position can be liquidated. Orders execute on the protocol and remain active until filled or cancelled.* Use conservative leverage, size the grid so you can carry a full range breakout, and read [Liquidation](https://dasus.gitbook.io/dasus-docs/trading-concepts/liquidation.md) before running a leveraged grid.
{% endhint %}

## Risk checklist

* Grid trading can lose your investment. It is not passive, guaranteed yield.
* Choose the range from where the market realistically trades, not only from recent highs and lows — the 30-day line in the preview is there for that.
* On perp grids, watch the [funding rate](https://dasus.gitbook.io/dasus-docs/trading-concepts/funding-rate.md): a persistently one-sided rate is a carry cost on the position the grid ends up holding.
* Start with a small investment and low or no leverage until you have seen a grid run in live conditions.

## Related pages

* [Order Types](https://dasus.gitbook.io/dasus-docs/trading/order-types.md) — the order types for manual trading
* [Margin & Leverage](https://dasus.gitbook.io/dasus-docs/trading-concepts/margining.md) — cross margin and leverage
* [Liquidation](https://dasus.gitbook.io/dasus-docs/trading-concepts/liquidation.md) — how and when positions are liquidated
* [Fees](https://dasus.gitbook.io/dasus-docs/the-app/fees.md) — how fees apply to every grid order


---

# 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://dasus.gitbook.io/dasus-docs/trading/grid-bots.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.
