Zupex streams signals
Zupex authenticates the agent, keeps the WebSocket session open, and sends ready pair-trading opportunities plus test/live permissions.
- Opportunity signals
- Heartbeat permissions
- WS proxy for monitoring
Agent-first crypto automation
Zupex streams model opportunities. Your Docker agent keeps exchange keys local, opens test or live trades, and records the ledger you can inspect later.
███████╗██╗ ██╗██████╗ ███████╗██╗ ██╗ ╚══███╔╝██║ ██║██╔══██╗██╔════╝╚██╗██╔╝ ███╔╝ ██║ ██║██████╔╝█████╗ ╚███╔╝ ███╔╝ ██║ ██║██╔═══╝ ██╔══╝ ██╔██╗ ███████╗╚██████╔╝██║ ███████╗██╔╝ ██╗ ╚══════╝ ╚═════╝ ╚═╝ ╚══════╝╚═╝ ╚═╝
How it works
Zupex streams opportunities over WebSocket. Your agent runs locally, talks to exchanges directly, and can proxy monitoring state back to the web and mobile app without moving custody.
Zupex authenticates the agent, keeps the WebSocket session open, and sends ready pair-trading opportunities plus test/live permissions.
The Docker agent runs on your machine or server. It keeps exchange keys local, evaluates each signal, and writes its own SQLite ledger.
The agent can route monitoring state through Zupex as a WebSocket proxy for web and mobile views, while funds and keys stay on your side.
FAQ
No. Funds stay on the user's exchange account. The agent uses exchange API keys configured by the user.
Detailed execution history stays in the local SQLite ledger. The agent can expose monitoring state through Zupex for web and mobile views.
Zupex sends authenticated heartbeat permissions and ready opportunity signals over the agent WebSocket.
Yes. Test mode uses local simulated trades, so exchange API keys are only needed when live execution is enabled.
Yes. The agent supports both modes independently, and live opens only run while subscription permission is active.
The agent prints a terminal dashboard every few seconds from local state, including open orders, PnL, and recent events.