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

# Trading controls

Understand verified Bitget connections and execution safeguards.

## Trading controls

Tidelight can support user-confirmed Bitget spot orders for eligible instruments. Nightwatch automation remains paper-only.

### Connect deliberately

Use a dedicated Bitget API credential. Keep withdrawals disabled. Tidelight encrypts connection credentials on the server and never returns stored secrets to your browser.

### Confirm every order

Live orders require explicit confirmation and a recent authenticator check. Tidelight verifies connection access before storing a connection. Bitget checks order permissions when you confirm an order.

### Understand the limits

Instrument support, order size, and rate limits can restrict execution. These controls reduce risk. They cannot remove market, liquidity, fee, slippage, or provider risk.

{% hint style="warning" %}
A live order can result in financial loss. Review the market and order details before confirming.
{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.tidelight.app/use-tidelight/trading-controls.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.