Ask your agent for a trade
How to request a trade evaluation from your agent. Agents evaluate trades on their own schedule via Radar, but you can also ask them directly.
← Trade overview · Radar overview
Quick start
- Open Commander or use the MCP tools
- Ask your agent to evaluate a coin (e.g., "Should I go long ETH?")
- The agent evaluates using its strategy at the next candle close
- Approve or Decline the result
How it works
When you ask an agent for a trade:
You ask → Agent evaluates → Decision ready → You approve or decline
- Request — You ask the agent to look at a trade
- Evaluate — The agent runs its strategy at the next candle close
- Decide — The agent returns Traded, No trade, Claimed, or Missed
- Act — You approve or decline the result
Where to ask
| Surface | How it works |
|---|---|
| Commander | Chat with your agent: "Look at BTC" or "Should I go long ETH?" |
| MCP | Use propose_entry_decision via API or third-party integrations |
The Trade screen itself is for manual orders only. To ask an agent, use Commander or MCP.
What the agent returns
The agent evaluates using its strategy and returns one of these results:
| Result | What it means |
|---|---|
| Traded | The agent found a valid setup and opened a trade |
| No trade | Conditions didn't match — no entry |
| Claimed | Another agent on the same team already holds a position on this coin |
| Missed | A valid signal existed but the entry window passed |
These are the same result labels used in Radar. See One trade per team per coin for how agents share coins.
Approving a trade
When the agent finds a valid setup, you can:
| Action | What happens |
|---|---|
| Approve | The trade executes using the strategy's entry policy |
| Decline | The opportunity is dismissed — no order placed |
If you don't respond before the entry window closes, the decision expires.
Good to know
- One request per team per coin — You can't request a second evaluation on the same coin for the same team until the first clears
- Candle close timing — The agent evaluates at the next candle close on its timeframe, not immediately
- Same strategy, same rules — The agent uses the same strategy it uses for Radar — no special evaluation
- Position conflicts — If the agent's team already has an open position on that coin, the agent can't open another
Advanced: how this relates to Radar
Asking an agent for a trade and Radar both use the same evaluation path:
| Surface | Who initiates | When it evaluates |
|---|---|---|
| Commander/MCP | You ask | Next candle close after your request |
| Radar | Automatic | Every candle close while deployed |
The strategy, risk rails, and execution are identical. The only difference is who starts the evaluation.
Advanced: request lifecycle
A trade request moves through these states:
- Pending — Waiting for the next candle close
- Evaluating — Agent is running the strategy
- Ready — Decision available for approval
- Completed — You approved, declined, or it expired
You can cancel a pending request before evaluation starts.
Related
- Commander — chat interface for asking agents
- MCP — API access for integrations
- Radar — automatic trade monitoring
- One trade per team per coin — how agents share coins
- Strategies — what the agent evaluates with