> For the complete documentation index, see [llms.txt](https://docs.tradesurge.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tradesurge.co/platform/terminal/place-a-trade.md).

# Place an R-sized trade

Enter one trade, confirm it, and TradeSurge sizes and sends it with a stop resting on the exchange.

This page walks through one manual entry from the Terminal. You set the idea, TradeSurge does the sizing and the checks.

## What you need

* At least one connected account (see [Connect Bybit](/platform/accounts/connect-bybit.md)).
* A risk dial set on that account (see [Set the risk dial](/platform/risk/risk-dial.md)).
* An authenticator app enrolled, which the app requires.

## Place the trade

{% stepper %}
{% step %}

### Choose the accounts

Tick every account this trade should go to in the account selector.
{% endstep %}

{% step %}

### Set direction and stop

Pick long or short, then set your stop price. The stop defines 1R for every account.
{% endstep %}

{% step %}

### Review the confirm card

The card shows each account, its size and any rule warning. Check the breach panel for any account close to a limit.
{% endstep %}

{% step %}

### Confirm

TradeSurge runs its pre-send checks and sends each leg with its stop attached.
{% endstep %}

{% step %}

### Read the result

Each account shows executed, failed or expired, with a reason.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
The most common refusal is an account near its daily limit. Breach Guard blocks new entries once an account passes its safety margin, so that leg is refused while the others go through.
{% endhint %}

## Good to know

* Pre-send checks include margin headroom. Market orders are checked against the top of the book before sending. Fills can still slip.
* Hard caps apply per order, per day, on open positions and on leverage.
* Close, flatten and kill switch are never blocked by these checks.

## Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Copy a trade across accounts</strong></td><td>How sizing and refusals work per account.</td><td><a href="/platform/terminal/copy-across-accounts.md">Copy a trade across accounts</a></td></tr><tr><td><strong>Close, flatten and the kill switch</strong></td><td>How to get out fast.</td><td><a href="/platform/risk/kill-switch.md">Close, flatten and the kill switch</a></td></tr></tbody></table>


---

# 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.tradesurge.co/platform/terminal/place-a-trade.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.