Skip to main content

Managing Radar

How to pause, resume, and remove coins from Radar, plus coin limits and programmatic control.

Pause and resume​

Pause a Radar setup​

Pausing stops monitoring but keeps your rules saved.

What happens when you pause
No new trades can open on this coin for the team — another team's setup of the coin keeps trading
Open positions continue to be managed
Exit rules still trigger normally
Rules and agents are preserved

Use pause when: You want to temporarily stop trading a coin without losing your setup.

Resume a paused setup​

When you resume:

What happens
Rules start matching again
Agents go on duty based on current conditions
New trades can open

Note: Resuming doesn't immediately open a trade. It just starts monitoring again — your agent still needs to qualify.


Remove a coin​

Removing a coin deletes its Radar setup entirely:

What happens when you remove
Monitoring stops immediately
All rules for this coin are deleted
Open positions continue under the owning agent
You can add a different coin (frees a slot)

Warning: Remove is permanent. To get the coin back, you'll need to recreate the entire setup.

Open trades when removing​

If you remove a coin while a trade is open:

  • The trade stays open
  • The owning agent continues to manage it
  • Exit rules still trigger
  • Once the trade closes, the coin is fully removed

Coin limit​

You can only have so many coins on Radar at once. The limit is platform-configured and shown in your dashboard. It counts Radar setups, so a coin you put on Radar for two teams counts twice.

TierExample limit
Standard5–10 coins
Premium20+ coins

Note: Actual limits are configured by BattleGrid administrators and may vary.

Checking your limit​

Look at the Radar summary panel:

MetricExample
Coins active7
Coins limit10

What if you hit the limit?​

ActionResult
Try to add a new coinBlocked — "Coin limit reached"
Remove an existing coinFrees a slot
Pause a coinDoes NOT free a slot

Tip: Paused coins still count against your limit. To free a slot, you must remove the coin.


Conflict handling​

If the Radar setup changed while you were editing (e.g., in another browser tab), your save is refused to prevent overwriting someone else's changes.

SituationWhat to do
"Setup has changed" errorReload the page and re-apply your edits
Edits won't saveCheck if another session is open

Commander and MCP​

You can manage Radar programmatically using Commander or MCP.

Available actions​

ActionCommanderMCP
Add coin to Radar✓✓
Remove coin✓✓
Pause/resume setup✓✓
Edit rules✓✓
Change default agent✓✓
Read live status✓✓
Get activity log✓✓

Example: Add a coin via Commander​

In the Commander chat:

Add BTC to Radar with Trend Rider as the default agent.

Commander will:

  1. Create a Radar setup for BTC
  2. Set Trend Rider as the default agent
  3. Start monitoring

Example: Manage via MCP​

Through the MCP API, you can:

  • List Radar setups: See all your coins on Radar, each with its team
  • Create Radar setup: Add a coin with rules
  • Update Radar setup: Change rules or agents
  • Delete Radar setup: Remove a coin
  • Pause/resume: Toggle monitoring

Every Radar tool names the team with the coin. Leave the team out and it uses your Main team — except when committing a setup, which always names its team.

See MCP overview for API details.


Preview mode​

Before saving changes, use preview to see what Radar would do:

Preview shows
Which rules would match right now
Which agent would go on duty
Current regime reading
Whether the agent would qualify

Use preview when: Testing rule changes before committing them.


Good to know​

  • Paused coins count against your limit. Only removing frees a slot.

  • Open trades survive removal. The agent manages the position until it closes.

  • Rules are specific to a coin and a team. Each team's setup of a coin has its own rules — changing Main's BTC rules doesn't affect ETH, or Swing's BTC.

  • Commander uses natural language. You don't need to know API syntax — just describe what you want.

  • MCP is machine-friendly. Use it for automation, bots, or custom integrations.


Advanced: How Radar fits the stack
LayerWhat it owns
StrategyIndicators, rules, agent instructions, entry, levels, exit
AgentAssigned strategy, risk limits, one account slot
RadarWhich of a team's agents are on duty for this coin, when, and at what confidence floor

Radar doesn't change your strategy or agent settings. It just decides when each agent is active on a coin.

Commander and MCP can manage Radar setups but can't modify the underlying strategies directly from the Radar context.

Advanced: Bulk operations via MCP

For managing many coins at once, use MCP to:

  • Batch add: Add multiple coins with the same rule structure
  • Batch pause: Pause all setups matching a condition
  • Batch update: Apply the same rule change across coins

This is faster than editing coins one by one in the UI.

See MCP overview for available endpoints.


← Radar overview · Troubleshooting · Live status