Protocols & tool counts

The landing says 185 protocol tools across 12 protocol integrations. This page is the arithmetic behind that sentence, so you don’t have to take it on faith.

The count comes from one file in the Vex source, src/vex-agent/tools/protocols/catalog.ts, where each protocol namespace binds a manifest of tools. Summing the manifests gives the in-app number below. Studio has a separate export inventory: 184 protocol tools plus 29 internal tools, 213 in total. Its generated inventory is checked against the live MCP export in CI.

Vex’s internal tools (wallet balances, chain reads, token checks, research, the prepare and confirm pairs) are counted separately and are not in this table. 29 of them are exported to Vex Studio.

Per-namespace counts

Inside a Vex session the agent does not see all 185 schemas at once. Protocol tools are reached through ToolSearch, a discovery step that adds only the tools you matched to the tool list as real function schemas, callable from the next message onward. See Agent sessions. Over MCP the rule is different: the tool list has to be identical for every client, so all 184 exported protocol tools are listed and directly callable. The desktop-only launchpads.images locker listing stays inside the app, accounting for the one-tool difference. The exported vex_ToolSearch is a read-only catalog search.

Integrations, not executions

We write protocol integrations rather than “executes across 12protocols” because the namespaces are not all the same kind of thing. One of them executes nothing at all: dexscreener (18 tools) is market data, pairs, prices, candles, trending and top traders, and every tool in it is read-only.

The rest mix reads with writes in different proportions. solana carries 34 tools, and most of them read: Jupiter swaps and lend deposits execute, while the prediction surface is mostly order books, positions and history. morpho (19) and pendle(29) each pair market and position reads with real mutations, supply, borrow, repay, withdraw, mint, redeem and claim. Counting a screener as a place Vex “trades” would be a false claim, so we don’t make it.

lighter(40) is the newest namespace and now the largest. It is an order-book exchange rather than an AMM, so the split is different again: market, order-book, candle and trade-tape reads sit beside authenticated account, position and order reads, and the write side covers deposits, order create, modify, cancel and cancel-all, reduce-only position close, native OCO protection, withdrawals and their claims, plus the two setup paths that make managed trading possible at all, registering a local trading key and authorizing Vex’s trading fee. See Lighter trading.

The venues Vex actually executes on are KyberSwap and Uniswap for EVM swaps, Jupiter for Solana swaps, lending and predictions, Khalani and Relay for bridging, Morpho for lending, Pendle for yield positions, Lighter for perpetual and spot order-book trading on Lighter Core and Robinhood Chain, and pools.fun and Virtuals for launches and launchpad trading. Every one of those executions is an approval you click in a restricted session. See Approvals & the Safety Contract.

Chain coverage

Coverage is per integration, not a single global list. What the source registries actually carry:

The KyberSwap lane covers Ethereum, BSC, Arbitrum, Polygon, Optimism, Avalanche, Base, Linea, Mantle, Sonic, Berachain, Ronin, Unichain, HyperEVM, Plasma, Monad, MegaETH, Robinhood Chain, Arc. Solana is a first-class second family with its own locally generated keystore, not a wrapped EVM address; see Wallets & custody. Robinhood Chain is an Arbitrum Orbit L2 settling to Ethereum, with ETH for gas, and is where both launchpads and the $VEX token live.

Chain coverage is verified against the Kairos chain registry, and Studio counts against its generated MCP inventory.

How installer downloads are counted

The homepage’s 6,000+ milestone is rounded down from 6,149 installer asset downloads, verified on 2026-10-11 against the public GitHub release counters.

We add the download counters for DMG, EXE, AppImage and DEB assets across published releases, excluding drafts and prereleases. Updater manifests, blockmaps and ZIP archives are excluded. Repeat downloads still count, so this measures installer downloads rather than unique users or successful installations. The snapshot is refreshed when release facts are updated.

Keeping the numbers honest

Every number on this site is rendered from a single file, lib/facts.ts, with the source it was counted from noted beside it. This table is generated from the same array the landing’s stats band reads, so the two cannot drift apart. Updating the counts on a release bump is one file, one edit.