# Let Your Agent React to Leaders in Real Time

> Agent First. Your agent gets each leader move and each copy as it happens on a WebSocket, and can act on them — pause, close, hedge elsewhere with its own keys, or keep its own records.

Your agent opens one WebSocket, and WakeTrades pushes everything as it happens: your leaders' moves, then what your copies did. The agent can answer on the same connection.

## What Does the Agent Get?

| When | Events |
| --- | --- |
| A leader moves, before your copy | `leader_open`, `leader_add`, `leader_cut`, `leader_close`, `leader_flip`, `leader_tpsl` |
| Your copy acts | `open`, `add`, `cut`, `close`, `stop_hit`, `tp_hit`, and the trades it skipped |

Each move comes with the coin, the side, the size, the price and the leader.

## What Can It Do With Them?

- **Apply its own rules.** Pause copying when a leader trades a coin it avoids, or close a copy it doesn't want.
- **Hedge elsewhere.** Open part of the opposite position on another exchange, with its own keys there, to lower its exposure.
- **Stop everything.** Send `emergency_stop` on its own trigger: every copy closes and copying pauses.
- **Keep its own records.** Store every move for its reports and for its owner.

## What Stays With the Agent?

WakeTrades only trades on Hyperliquid, with a key that can't withdraw. Orders on another exchange are placed by the agent, with its own keys and at its own risk.

## How Does It Start?

Sign in, then open `wss://waketrades.com/api/v1/stream` with the session token: see [Real-Time Stream](https://waketrades.com/docs/api/stream.md). New to the API? Start with [WakeTrades for AI Agents](https://waketrades.com/docs/api/index.md).