Getting started

The first hour, in four steps

Three of these are reversible and the fourth is not, which is why the order is what it is.

  1. 1

    Connect a broker account

    Use an account you already own. For most people that means creating an API key at the broker and pasting it once. It is encrypted and read only at the moment an order is placed.

    Start with a paper account. Three of the four connections have one, and it costs nothing to be wrong there.

  2. 2

    Build a rule

    Pick a symbol and a timeframe, then write the conditions that open the position and the ones that close it. Sizing, stop and target are part of the same declaration, not a second screen you can forget.

    If you ask for something the engine cannot evaluate, it is refused there and then. A rule that looks fine and never fires is the failure this is designed to prevent.

  3. 3

    Let it run on paper

    Activate it against the paper account and leave it. The path is identical to live: same evaluation, same order construction, same lifecycle. Only the account it reaches differs.

    Watch a full round trip, entry through exit, before you go further. A rule that has never closed a position has not been tested.

  4. 4

    Point it at the real account

    Switch the strategy to your funded account. Set the per-trade ceiling and the concentration limit to numbers you would accept losing, and check where the kill switch is.

    This is the step that cannot be undone. Everything before it was a rehearsal, and this one sends real orders.

From outside

Two ways something else can reach in

Both are optional. Neither is required to use the product, and they behave differently on purpose.

Signals over a webhook

An outside charting tool can send entry or exit for either direction. These arrive as instructions rather than proposals, because an incoming alert carries no reasoning anyone here can check, so the risk limits are what stands between it and your account.

An AI client over the agent surface

Connect a client and it can read your state and write proposals. It cannot confirm one: that is a permission no machine identity on that surface can hold, so nothing reaches your broker until you approve it in the app.