Essential Controls for Safely Copying a Trading Strategy
Learn the core limits, authority separation, and monitoring practices that keep capital safe when you copy an existing trading strategy in real.
Produced with automation, then checked by deterministic quality rules and an independent source-grounded review before publication.
- 01Owner signed limits cap order size, daily exposure and loss for any copied strategy.
- 02Agent keys are scoped to order placement only, preventing unauthorized withdrawals.
- 03An emergency stop revokes the active agent key without automatically liquidating positions.
- 04Market data must include source, timestamp and freshness checks before use.
- 05Regular reconciliation of order outcomes avoids false assumptions about execution.
A copied trading strategy must operate within explicit risk boundaries set by the owner. The owner defines limits on order size, daily notional exposure, and loss tolerance. These limits are enforced by scoped agent keys and can be adjusted at any time.
How does core Limits That Protect a Copied Strategy work?
- The owner can set a maximum order size per trade to avoid outsized positions.
- A daily notional limit caps the total value of all orders in a 24 hour window.
- A daily loss limit stops the agent once cumulative losses reach a predefined threshold.
- An expiry timestamp can be attached to the agent authority, disabling it after a set period.
- Custom policy fields may be added to match specific risk appetites.
How Agent Key Scoping Reduces Operational Risk?
Agent keys are granted only the permissions needed for order placement and cannot initiate withdrawals, change owner limits, or modify other agents.
- Trade scoped keys allow order placement but not fund withdrawal.
- Limits are enforced at the key level, so each trade respects the owner policy.
- Revoking the key instantly stops further activity without affecting existing positions.
Emergency Stop Mechanics and Their Limits
When an emergency stop is triggered the calling agent key is revoked, halting any new orders. The stop does not automatically liquidate open positions or cancel token allowances; those actions require a separate owner signed transaction.
- The stop is immediate for new activity, reducing further exposure.
- Existing positions remain until the owner decides to close them.
- Token allowances must be manually revoked to prevent future spend.
Ensuring Market Data Quality for Automated Decisions
Reliable market data is the foundation of any automated decision. Each price tick should include a source identifier, a timestamp and a freshness indicator. Missing or stale data must be flagged and never treated as zero.
- Validate the source of each price tick before using it.
- Check timestamps against a known clock to ensure freshness.
- Implement warnings for gaps or anomalies in the data stream.
Reconciliation Practices to Avoid False Assumptions
A timeout does not prove an order failed, so durable mutation identity and explicit error handling are required. Record each order's unique identifier, query the venue for final status, and adjust internal balances only after confirmation.
- Store the order ID and expected fill details.
- Query the venue for the final status before assuming success or failure.
- Adjust internal balances only after confirmation to avoid deviation.
"Controls are only as strong as the processes that enforce them; a copied strategy without limits is a liability, not an advantage."
Related Reading
For a broader view of risk limits see the article on Essential Risk Limits Every AI Trading Agent Should Enforce. Details on daily notional limits are covered in Understanding What a Daily Notional Limit Controls for a Trading Agent. Guidance on building robust controls can be found in How to Build an AI Trading Bot with Robust Risk Controls.
Frequently asked questions
Owner authority can set limits, approve withdrawals and revoke keys, while agent authority is limited to placing orders within those predefined limits.
Yes, the owner can update signed limits at any time; the new limits take effect on the next order submission.
No, an emergency stop only revokes the agent key. Closing positions requires a separate owner signed transaction.
Reconciliation should occur after every batch of orders and at regular intervals, such as hourly, to catch mismatches promptly.
Flag the data, halt order generation until fresh data arrives, and never treat missing values as zero.
Sources and verification
Product claims in this article were checked against these first-party references. Runtime status remains authoritative for current availability.
- Felix documentationfirst party
- Felix machine referencefirst party
Build with Felix now.
Felix infrastructure is live through MCP and the API. The Felix V1 retail quant-desk private beta is planned for September 22.
AI trading bots continuously process market data, use trained models to create trade signals, and convert those signals into signed orders while enforcing strict risk controls and safety checks.
Owner authority grants full control over accounts and policies, while agent authority operates under scoped limits. This guide clarifies their differences, key controls, and safety measures for automated trading.