SahanAI settings

Your broker key

Used to place paper orders on your own Alpaca paper account when you run the platform: every paper run trades there, and nothing is simulated inside the platform on your behalf. Live broker keys are not accepted yet.

Alpaca's paper account exercises real order formats and multi-leg handling, but Alpaca simulates the fills on its own market data, which can differ from the platform's, and fill realism varies. It does not say how a live account would fill, and it does not check the permissions (such as the options approval level) a live account would need. Every sleeve, trade and report is labelled with where it traded.

Every venue the platform knows, and what to know about each

    Checking...

    When you save, the key is checked with Alpaca (a read-only request to your paper account) and, if Alpaca accepts it, stored encrypted. It is never shown again: only the last four characters of the key ID appear here. If the check cannot be made, nothing is stored.

    Notifications

    Where to tell you about what the platform does: an entry, an exit, a risk refusal, a kill switch, an approval waiting for you. A destination only receives anything after you prove it is yours: we send it a six-digit code and you type it back here.

    Level alerts

    Tell me once when a price crosses a level: a price you type, or the gamma flip or a wall of the dealer map, which move with the market. You are told on the destinations above, at the severity you chose there, and the alert also shows on the dashboard. A rule that is made while the price is already past its level waits for the next crossing; the Api looks at each dealer map it receives, so it watches only symbols the platform is following.

    No level alerts yet.

    TradingView alerts

    Let a TradingView alert tell you something here: make an endpoint, then paste its address and message into the alert. Each call becomes an alert on the destinations above. It only ever alerts you; it never places an order.

    No endpoints yet.

    Browser notifications

    Show an alert on this computer or phone as a notification, even with the page closed. Choose the least severe alert you want on each device. A phone needs this site to be reached over https.

    Checking...

    No devices yet.

    Your account

    At least 12 characters, not your email address, not a common password. Changing it needs a code from your authenticator app, and ends your other sessions.

    If you think someone else may have your session, end every session of this account, this one included. You will sign in again with your password and a code.

    Code for trading actions

    Deciding an approval, sending a manual order, pausing or resuming a sleeve and releasing a kill switch ask for a code from your authenticator. Stopping trading never does. Changing this asks for a code.

    Trusted browsers

    A browser you trusted when you signed in asks for your password but not a code, for 30 days. Signing out everywhere, or changing your password, stops trusting them all.

    Prepare a run

    Start a core host on this machine with your stored key instead of environment variables. You get a code that works once, for ten minutes, and is shown only here. The host redeems it at start-up from this server over a local connection and keeps the key in memory.

    Market data

    Market data comes from one key that the platform's administrator sets for everyone. You do not need to provide one.