What is Vex

Vex is a desktop application for macOS, Windows and Linux that runs an autonomous crypto agent on your own machine, next to a wallet the app generates and encrypts locally. The agent can research markets, quote and execute swaps, bridge across chains, and run time-boxed autonomous missions, while every fund-moving action is, by default, gated behind your explicit approval inside the app.

There is no custodian, no server-side signing and no cloud key storage. The product’s own summary: “Your keys. Your machine. Your agent.”

What it does

• Agent sessions. Chat sessions that chain real on-chain tools: balances, research, quotes, swaps, bridges. See Agent sessions.
• Missions. Co-planned contracts (goal, capital ceiling, deadline) the agent then pursues unattended, inside a hard deadline it cannot move. See Missions.
• Approvals. Every mutating action becomes an intent you act on, risk-labelled from info to critical. See Approvals & the Safety Contract.
• Boards. Agent-composed market analysis (Token Radar) beside your portfolio. See Boards & Token Radar.
• Vex Studio. The tool surface exposed to 15 coding agents over MCP, with approvals still in the app. See Vex Studio.

That surface spans 140 protocol tools across 11 protocol integrations, counted namespace by namespace here.

What self-custodial means here

Wallets (EVM and Solana) are generated on your machine and sealed in AES-256-GCM keystore files under a master password hardened with scrypt N=2¹⁷. Conversations, memory and embeddings live in a local Postgres bound to 127.0.0.1, inside Docker containers the app manages for you. Inference goes through your own OpenRouter account. The only things that leave your machine are the calls the work requires: public chains, protocol APIs, your model provider, and the activity feed covered in Privacy.

What’s the catch

• You need Docker and an OpenRouter API key. See Requirements.
• Vex charges a 25 bps fee on successful swaps, bridges and launches. Quotes, reads and research are free. See Fees.
• Self-custody cuts both ways: a lost master password or a deleted config directory means lost keys. See What Vex can’t protect.

Source-available, not open source

The code is public at github.com/Vex-Foundation/Vex so its claims can be checked: free of charge, you may read, audit and run it, and use the official builds to self-custody your own assets for personal, non-commercial purposes. Redistribution, forks and commercial use are not licensed, so it is not OSI open source, and this documentation doesn’t call it that.