> For the complete documentation index, see [llms.txt](https://nadobro.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://nadobro.gitbook.io/docs/core-features/editor.md).

# Text-to-Trade

Natural language trade parsing — just type what you want to trade.

**Text-to-Trade** is NadoBro's natural-language trade entry. Type a trade in plain English; NadoBro parses, builds a confirmation card, and waits for you to tap **Confirm** before anything is signed.

### Grammar

The parser handles direction, size, asset, and leverage in any reasonable order. \
All of these work:

> \- long 0.1 BTC 10x\
> \- buy 0.5 ETH 5x\
> \- short 100 SOL 3x\
> \- sell BTC 0.05 20x

<figure><img src="https://910128549-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE86l2mtcpE8vOEj0JuxR%2Fuploads%2F6KpDmzW5FQPG2wXNgErI%2FScreenshot%202026-03-22%20at%209.08.49%E2%80%AFPM.png?alt=media&amp;token=0b28fb48-5dff-456c-ba07-648f97afb52a" alt=""><figcaption></figcaption></figure>

\
One of NadoBro's core feature is natural language trade parsing. Just type what you want to trade in plain English and done. NadoBro understands your intent and executes accordingly.<br>

### **The confirmation card**

Before anything is sent to Nado, NadoBro renders a card showing:

* **Direction, size, asset, leverage.**
* **Notional in USDT0** and the margin reserved.
* **Estimated fees** (taker, maker rebate, builder fee).
* **Liquidation price** and per-asset max leverage.
* **Network** (Testnet / Mainnet) — color-coded so you don't mix them up.
* **Confirm / Cancel** buttons.

Nothing is signed until you tap **Confirm**. The card times out after a short window for safety.

#### Persistent confirmations

Pending trade confirmations are **persisted across worker restarts**. If the bot's worker bounces between you sending a trade and tapping Confirm, the card stays valid — the confirmation will still execute correctly.

#### What happens after Confirm

1. NadoBro validates product, balance, price, leverage, and isolated-only rules.
2. The order is submitted via the Nado SDK with `post_only` / `reduce_only` / `trigger` set as appropriate.
3. A trade row is inserted in NadoBro's local ledger.
4. **Archive fill sync** resolves the final fill, fees, slippage, and realized PnL from the Nado indexer.
5. The runtime reconciles strategy and exchange state on the next cycle.

#### Supported Keywords

| Keyword          | Meaning                         | Example                  |
| ---------------- | ------------------------------- | ------------------------ |
| buy / long       | Open a long position            | `long BTC 10x`           |
| sell / short     | Open a short position           | `short ETH 5x`           |
| market           | Execute at current market price | `buy BTC 5x market`      |
| limit \[price]   | Execute at specified price      | `long ETH 5x limit 3200` |
| tp \[price]      | Take profit price               | `long BTC 10x tp 95000`  |
| sl \[price]      | Stop loss price                 | `long BTC 10x sl 85000`  |
| \[N]x            | Leverage multiplier             | `long BTC 20x`           |
| \[size] \[asset] | Position size                   | `buy 0.5 BTC 10x`        |

{% hint style="info" %} <sup>**NadoBro parses your intent — you don't need exact syntax. Just include the key info: direction, asset, size, and leverage. The order of keywords is flexible.**</sup>
{% endhint %}


---

# 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://nadobro.gitbook.io/docs/core-features/editor.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.