ORACULUM/ BOTSFAQStart free

Frequently asked questions

Automated trading on Interactive Brokers, answered plainly.

Is my money safe? Does Oraculum Bots hold my funds?

No — we never take custody of your money. The bot trades inside your own Interactive Brokers account using trade-only permissions, so it can place and manage orders but cannot withdraw or transfer funds. Your capital stays with your broker at all times.

Do I need an Interactive Brokers account?

Yes. Oraculum Bots runs the strategy in your own IBKR account, which is what keeps you in custody of your funds. You connect it once when you create a bot; a free IBKR paper account is enough to start with no real money at risk.

Do I need to know how to code?

No. You configure the strategy from a simple interface — risk level, leverage, instruments — with no programming and no wrestling with the IBKR API. An AI assistant can also translate a plain-English description of your risk appetite into a valid configuration.

What strategy does the bot run?

A volatility-targeted, systematic trend-following (time-series momentum) strategy across liquid futures. It sizes positions from recent realised volatility rather than conviction and caps gross exposure at the leverage you choose. It is built for steady, risk-adjusted participation, not outsized bets.

What is the difference between paper and live trading?

Paper trading runs the exact same strategy on live market data using a simulated IBKR account, so no real money is ever at risk — it is how you validate a configuration before committing capital. Live trading executes the same logic in your funded account. You choose when, if ever, to switch from paper to live.

How much does it cost?

You can start on paper for free. Oraculum Bots is currently in a limited private beta while we scale carefully; if the beta is full you can join the waitlist. Pricing for live accounts will be published before it applies to you.

What markets and instruments does it trade?

Liquid futures — equity indices (ES, NQ), rates (ZN, ZB), metals (GC), energy (CL), FX (6E) and more — through Interactive Brokers. Additional brokers, venues, and strategies are on the roadmap and are clearly marked as such.

What is the weekly re-authentication?

Interactive Brokers requires a periodic two-factor approval to keep a live session active — roughly once a week you tap an approval in your IB Key mobile app. Only you can approve it; we cannot do it for you. Until you do, the bot pauses new orders while your open positions are untouched, and it resumes automatically once approved. Paper accounts never ask.

Can Oraculum Bots guarantee profits?

No, and any service that promises guaranteed returns should be treated with suspicion. Trading involves substantial risk of loss, and no strategy — systematic or otherwise — can guarantee a result. We show metrics as they are, with disclaimers, and encourage validating on paper first.

What is the AI assistant and how does it work?

It turns a plain-English description of your goals into a configuration for the trend-following strategy, within hard guardrails: every value it proposes is clamped to safe bounds and scored on an out-of-sample backtest before you apply anything. It only ever suggests a configuration — it never places trades on its own.

Can I change or stop the bot at any time?

Yes. You can pause, restart, reconfigure, or delete a bot from the dashboard whenever you like. Going live is always a deliberate, separate action you take — nothing trades real money until you switch it on.

How are my Interactive Brokers credentials stored?

Your broker login is handled server-side and sealed in an isolated, per-tenant secret scoped to trade-only permissions — it is never exposed in the browser or shared across accounts. If you use your own AI provider key, it is encrypted at rest and never returned to the browser.

New to systematic trading? Read what trend-following is, how to automate an Interactive Brokers account, or paper vs live trading.

Start free on paper

Still have a question? admin@oraculum.network