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

# LiquidBots

![](https://235883712-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fal7c4dgI3wNP7Wwf2iT8%2Fuploads%2Fxw7eaAO2GFHQFFZJUAw3%2FFrame%205.png?alt=media\&token=023416da-bba3-43ea-8f12-420d5dc944ae)

**Automated trading strategies on Hyperliquid, on-chain and self-custodial.**

LiquidBots runs grid bots for you on Hyperliquid. You pick the market, the direction and the range. The bot places a ladder of orders across it and gets paid each time price swings from one level to the next and back.

{% hint style="success" %}
**New here?** Start with the [How To Guides](/how-to-guides.md). They take you from a fresh wallet to a running bot.
{% endhint %}

## Live today

* **Long, short and neutral grid bots** on every native Hyperliquid perps market, up to 10x leverage
* **Up to 150 grid levels**, arithmetic or geometric spacing, with range, stop loss and take profit set by dragging on the chart
* **Backtesting:** run your exact settings against historical prices before you fund a bot
* **Trigger price entry:** the bot waits until price reaches your level, then starts itself
* **Take profit and stop loss** by price or percentage, editable while the bot runs
* **Live margin health,** plus the ability to reinforce it without stopping the grid: a configurable buffer, health warnings and adding margin to a running bot
* **Multiple Trader Accounts,** so you can run more than one grid on the same market
* **Telegram alerts**
* **MCP server:** drive your bots from Claude, ChatGPT or Grok

## Why it's built this way

* **Self-custodial.** Your Trader Account is owned by your wallet. No KYC to deposit, and you can withdraw at any time.
* **No API keys.** You never create, paste or share one.
* **No conflict of interest.** We sit above Hyperliquid, with no order book or liquidity of our own, and we're never the other side of your trade.
* **Audited.** Core contracts audited by Zenith, March 2026: zero critical, zero high-severity findings. [Read the report](/security-and-audits.md).

## In development

Vaults, so you can deposit with a strategist who runs the bots, and more strategy types. We'll announce each one when it ships.

***


---

# 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.liquidbots.xyz/liquidbots-the-command-layer-for-derivatives.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.