FST Broker Support Is Account-Specific, Capability-Certified, and Fail-Closed
QuantSignals exposes connection breadth without pretending that every connected institution, region, account, asset, or operation has equal execution capability.
Key Takeaways
- QS paper brokerage is the default evaluation destination and does not require a live broker.
- Cloud OAuth/API connections and local agent-companion connections are separate lanes with different operational requirements.
- QS Broker Link provides compatibility breadth, while native integrations are preferred for deeper agent-grade execution.
- Connected and readable do not mean tradable; stock, options, and AUTO capability are certified separately for each account.
- The live broker catalog and account capability verdict inside QS are the source of truth because provider availability can change.
Broker Capability Guide Compared
| # | Agent / Tool | Category | Runs on | Autonomy | Best for |
|---|---|---|---|---|---|
| 1 | QS Brokerage Paper | Native paper rail | Web, desktop, CLI, mobile | Full supervised session testing | Evaluating FST behavior without risking live capital |
| 2 | QS Native / Direct Broker | Certified direct integration | Cloud or approved hosted connection | Capability-dependent | Agent-grade execution where the exact account and operations have been verified |
| 3 | QS Broker Link | Compatibility connection | Cloud connection portal | Runtime-gated by underlying account capability | Broad account discovery and transitional broker coverage |
| 4 | Local Agent Companion | Local gateway connection | User-controlled desktop or gateway | Capability-dependent | Brokers whose official architecture requires local software or a gateway |
How QuantSignals Classifies Broker Access
QS Brokerage is the native paper and house execution rail. Direct broker integrations connect through an approved hosted MCP, OAuth/API, or signed API workflow when QuantSignals can enforce the common account, risk, preview, write, and reconciliation contract. QS Broker Link provides broader compatibility while native coverage expands.
Some brokers require a local gateway or desktop companion and are not appropriate for a pure cloud OAuth flow. Those connections belong in a separate local companion lane so credentials and broker-specific unlock material are never collected through chat or ordinary web forms.
Broker support is intentionally expressed as capabilities rather than a static logo wall. The system evaluates connection status, portfolio reads, stock writes, options writes, cancellation, close, reconciliation, environment, degradation, and account selection before showing a destination as AUTO eligible.
How It Works
- Connect — Authorize through the supported provider flow without sharing broker passwords or private secrets in chat.
- Select the exact account — Bind reads and writes to a stable provider-scoped account instead of assuming a default.
- Verify reads — Confirm account, portfolio, positions, and authoritative order state.
- Certify operations — Test preview, place, cancel, close, idempotency, and reconciliation for the requested asset and environment.
- Promote to AUTO — Show the account in the AUTO picker only after the complete FST session contract passes.
Frequently Asked Questions
Which brokers does FST support?
FST supports QS paper brokerage plus accounts exposed by the current QS broker catalog. Exact read, stock, options, and AUTO capabilities are verified per provider, connection, account, region, environment, asset, and operation, so the in-product capability verdict is authoritative.
Does a connected broker automatically support live FST trading?
No. Connected is only the first capability level. Portfolio reads, stock writes, options writes, cancellation, close, reconciliation, and a complete supervised session must be verified separately.
What is QS Broker Link?
QS Broker Link is the compatibility lane used to connect a broader range of institutions behind the same QS account and capability contract while native integrations expand.
Why are some brokers handled by a local companion?
Some official broker architectures require a local gateway or desktop service. A user-controlled companion preserves that requirement without asking users to transmit sensitive broker credentials through chat.
Install FST 2.0 (desktop CLI & mobile app) · See QuantSignals V6