Monko Onboarding: The Complete Omni Bucko + TradersPost Setup Guide

Monko’s futures setup depends on the platform of the account you want to trade. Choose your platform in the collapsed “I use Tradovate” or “I use ProjectX” setup questions below. This guide does not choose a route or enable an account for you.

What is available

Tradovate monitored brackets send automatic market-entry instructions with a fixed stop and target through TradersPost. Bucko monitors the exact linked Tradovate account using its separate native connection. This mode is available through explicit account binding and acknowledgement; existing users are not automatically migrated or enabled.

ProjectX via TradersPost is a separate automatic entry relay. Protection and exits belong to the trading platform, and broker fills, protective orders and daily P&L are unverified in Bucko on that relay.

Manual TradersPost tickets, standalone stop replacement, automatic re-arming and legacy trailing management remain unavailable. A connected broker badge does not enable those features. If you use both platforms, preserve the saved mode on each account and review any mixed-route restriction shown by Monko.

Shared setup checklist

1. ▸Identify the exact broker account and platform. A prop-firm brand can offer more than one platform.
2. ▸Keep one dedicated TradersPost strategy/webhook per account. Do not reuse a managed webhook through a legacy alias or another execution mode.
3. ▸Open Monko Settings → Copy Trading and choose the instructions for that destination’s saved platform. Confirm required subscription settings in TradersPost’s actual order preview.
4. ▸Review quantity, symbol, timeframe, grade and session filters. A route being saved and acknowledged is separate from Monko being enabled in auto mode.
5. ▸Inspect delivery and broker evidence separately. Keep records and account bindings for unresolved executions.

Opening a platform’s instructions does not switch a saved route or renew an acknowledgement. Webhook and bound-account changes require an explicit new acknowledgement. Pausing new signals leaves existing broker orders and positions in place.

Fixed brackets and risk displays

In Tradovate monitored mode, Pine levels or the configured custom fixed bracket supply the stop and target. Custom dollar distances are per contract: a $100 stop with two contracts plans $200 of risk before fees and slippage. Contract quantity and portfolio exposure limits still apply.

Daily limits are entry budgets. They block new entries; they do not automatically flatten an existing monitored position or guarantee a maximum realized loss. Monko checks risk metrics the broker supplies. Unavailable trailing-drawdown or auto-liquidation metrics are not verified or enforced. Saved scheduled-flatten and consistency requirements block this mode until supported or explicitly resolved; choosing this mode does not remove saved constraints.

These statements do not describe a ProjectX relay risk check. On that route, review protection and caps in the trading platform, including whether they apply to external entries. Monko cannot verify them from a receipt.

Understand the activity log

• ▸Signal accepted: TradersPost acknowledged the request. This is not a fill.
• ▸Entry observed: Native Tradovate evidence identified an entry. Protection needs its own evidence.
• ▸Bracket observed: Native evidence identified the linked protective orders; current evidence can still become stale.
• ▸Execution awaiting confirmation / held: The result is unresolved. Another entry remains blocked while the original lifecycle is checked.
• ▸BROKER_READ_BLIND or incomplete inventory: Bucko could not verify required broker state. This does not prove a rejected stop or a flat account.

When a Tradovate connection expires or cannot be read, use Reconnect on that login’s existing Station row. Reconnecting preserves its identity and checks access to bound accounts. Do not select another platform to work around a read failure. If Bucko cannot verify exposure, check the broker’s positions and working orders directly.

ProjectX relay delivery uncertainty has its own account-specific Relay delivery status recovery. Resolve the original request in TradersPost and the trading platform before acknowledging it. That acknowledgement only allows future relay signals; it does not retry the original or modify a broker order.

Subscription reference material

Use the selected route’s checklist and compare signal values with the actual planned broker order. A blanket subscription fallback is not a substitute for checking the required overrides. None of these reference links enables a Monko route or proves an account ready.

• ▸Futures quantity rules
• ▸Signal override rules
• ▸Signal stop-loss rules
• ▸Pre-order cancellation
• ▸Entry cancellation delay
• ▸Exit cancellation delay
• ▸Exit order types
• ▸Planning-stage retries
• ▸TradersPost ProjectX limitations
• ▸TopstepX platform risk settings

Choose your platform below

Expand only the setup question matching the account you are configuring. Existing broker exposure and unresolved execution records must be reviewed before changing that account’s routing.