Brokerages and platforms that work with ChartXpert AI Options

No. Every analytics surface — SPX studies, gamma exposure, flow, contract measurements and alerts — works with no brokerage link at all. Linking a brokerage only adds your own positions and, if you separately consent, order routing.

The full analytics desk. You read the SPX tape, dealer positioning, flow and per-contract studies here, then place the trade inside Derayah. No credentials, no account link.

Yes. The compatibility matrix only describes account linking. Analytics is broker-independent: the desk reads the US options market itself, so a member on any brokerage — local or international — sees the same SPX and contract studies and simply executes wherever their account lives.

Yes. Both live and paper IBKR logins are supported on the connections screen — the pairing code you generate is bound to the environment you pick, so a paper session never reads or touches a live account. Members usually pair paper first to see the ledger fill in, then repeat the step for live.

Four steps. Example of a first link: you open the connections screen and authorize the account link (the scope catalogue lists what each permission reads); you pick a session path; the desk confirms the session is live and lists the brokerage accounts it can see; you choose the account to read and its positions, balances and option holdings appear in the portfolio ledger. Order routing is not part of this flow.

It links one bridge program on one machine to your desk account. You generate it on the connections screen, paste the shown command into PowerShell or a terminal beside IB Gateway / TWS, and the code is consumed once. A second machine needs a new code, and revoking the link invalidates it immediately.

Yes. A membership is activated first — every plan starts with a one-time three-day free trial — and the connections screen opens with it. That order exists so the account link is always attached to an identified member with an audit trail.

The managed session is the default: we host the brokerage session, so nothing has to stay running on your machine and the link survives a reboot. The local bridge suits members who prefer to keep the brokerage session on their own machine beside IB Gateway / TWS; it reads only while that program is running.

No. The link belongs to the account, not to a browser session, so signing back in shows the same linked account. It stops only when you revoke the consent, or — on the local path — when the bridge program is closed on your machine.

No. Order routing is a separate consent scope with its own acknowledgements, it is revocable at any time, and every command is written to an append-only audit trail. Revoking the consent removes the stored linkage.

Revocation purges the stored credentials, the bridge agents and the linked brokerage accounts, and the portfolio ledger stops reading. The audit trail of what happened while the link was active stays — it is append-only by design and cannot be edited or deleted.

The managed and local session paths authenticate against the brokerage itself. Where a credential must be held for a session, it is encrypted at rest and scoped to your account only; the desk never displays it back and never shares it.

Positions, option holdings, balances and the fills the brokerage reports for the linked account — the inputs the portfolio ledger and exposure views need. Personal profile details, funding instructions and statements are not read, and each member reads only their own linked account.

The session lists every account it can see and you choose which one the ledger reads. Switching to another account is the same choose-account step again — the previous selection stops being read as soon as you change it.