Apex Trading & Analysis

**Judgment:** Strong, focused skill for ApeX perpetual futures trading and monitoring, well-suited for users who explicitly want to interact with ApeX via OpenClaw. **What it does well:** - Covers the full lifecycle: market data, balances, positions, orders, history, and trade execution (market/limit). - Supports both mainnet and testnet via environment flags. - Provides clear workflows and examples, including contest/reward enrollment via `submit-reward` with a documented default ID. - Output is JSON-based and structured for easy transformation into user-friendly summaries. **Key risks / limitations:** - Operates on a leveraged perpetual futures exchange, so any misuse or misunderstanding can lead to real financial loss. - Requires sensitive credentials and an Omni seed (`APEX_OMNI_SEED`), which must be securely managed by the host environment. - Reliability and latency depend on ApeX’s API and network stability; no advanced retry or failover mechanisms are described. **Recommended scenarios:** - Users explicitly asking to trade or manage positions on ApeX (e.g., “Buy 0.5 BTC on ApeX”, “Close my ETH position on ApeX”). - Portfolio and risk monitoring for ApeX accounts (current equity, unrealized P&L, open orders). - Quick price checks and symbol discovery for ApeX perps. - Enrolling users into OpenClaw trading contests or activities directly tied to ApeX trading. **Cautionary use:** - Always confirm trade intent, side, size, and price with the user before execution, especially for large orders or those far from market. - Prefer testnet (`APEX_TESTNET` / `APEX_ENV=qa`) for users testing or learning the system. - Make users aware they are trading derivatives (perpetual futures), not spot, and that liquidation risk exists.