Paper trading is live. Strategy operations come next.
CuteMarkets now supports integrated paper accounts, orders, positions, fills, and portfolio history. The next product iteration is the workflow around it: review reports, strategy profiles, parity checks, alerts, bot templates, and community strategy pages.
REST
/v1/paper
MODE
paper
NEXT
review
What is next
The next major iteration is strategy operations around paper trading.
Order entry is only the first layer. The bigger product opportunity is making strategy promotion, review, automation, and sharing reproducible.
Strategy Workbench
Save strategy profiles with ticker universes, DTE windows, sizing rules, fill policies, risk limits, and linked paper accounts.
Paper review reports
Daily summaries for fills, no-trades, rejected orders, open positions, risk events, drawdown, and end-of-session status.
Backtest-to-paper parity
Compare the promoted research object with the paper route so timing, contract choice, quote checks, and rejects stay explainable.
Alerts and webhooks
Route fills, rejects, drawdown thresholds, stale orders, and strategy events to webhooks, Discord, Slack, or internal bots.
Bot runtime templates
Starter loops and SDK examples for agents that poll data, submit paper orders, persist state, and write review artifacts.
Community strategy pages
Share public strategy profiles, review notes, parameter ranges, and paper results without exposing private keys or account details.
Built for teams that need evidence before promotion.
The next workflow should connect market data, backtests, paper accounts, review reports, and shared strategy pages. A strategy should carry its assumptions with it, so every paper run can be explained and compared.
Paper execution
Paper accounts, orders, positions, fills, resets, and portfolio history are available in the dashboard and API.
Session evidence
Trades, no-trades, quote rejects, stale orders, and risk events become daily review objects instead of loose notes.
Research parity
Backtest artifacts and paper behavior can be compared before a strategy is promoted, parked, or killed.
Community pages
Publish strategy profiles, paper-run notes, and forks so other users can learn from reproducible setups.