MUTEX
Docs
 Home
Developers · Agent access

Agent access

Three ways to put an AI agent on Mutex, and the difference is blast radius: a bot key that can only trade one isolated bot, the assistant that never moves money without your click, or an agent key that acts as you, fenced to your own wallets.

MCP server docs tier 1: the bot-scoped trading key
Overview

The tiers

TierKeyWhat it is
Tier 1Bot keyA mtx_bot_…key bound to ONE isolated bot sub-account. Trade only; it cannot deposit, withdraw, or see the rest of your account. The bot's balance is the worst case. Setup: MCP server docs.
AssistantIn-appThe assistant inside the app. It reads your books and drafts one-time tasks; every money move is a confirm card only your click executes. No key leaves the app.
Tier 3Agent key + signing keyAn mtx_agent_… key that acts as you, plus a signing key a linked wallet authorizes. It trades and withdraws as you, but withdrawals go only to your own linked wallets; the signing key expires within 90 days and is revocable at any time. Runs on the same MCP server, in user mode.

Start with tier 1. It is the sanctioned safe way to let an agent trade real money: the bot's balance is a hard ceiling. Reach for an agent key only when the agent must move money in and out.

Tier 3

What the two keys are, and their limits

The agent keyis the agent's session: it trades across your account exactly as you can. The signing key is a secp256k1 key the agent holds on its own machine; one of your linked wallets signs a delegation that lets it sign withdrawals for you until a date you choose.

  • Withdrawals go only to your own linked wallets. The signer checks the destination against its own registry; any other address is refused.
  • Agents can never change linked wallets. Adding, replacing or removing a wallet takes a signature from a wallet you already linked, and the signing key is never accepted for that.
  • The delegation expires. 30 or 90 days, your choice; at most 90. Revoke, then authorize again to extend.
  • The switch is the master cut-off. Agent access is off by default; while it is off, every agent key is refused on every endpoint, reads included.
Setup

Connect an agent

  1. In the app, open https://app.mutex.exchange/settings > Agents and turn Agent access on.
  2. Under Agent key, click Create. The key is shown once, with the api host on a second line: paste both into the agent's environment (MUTEX_API_KEY and MUTEX_API_BASE). The agent can trade from here. One key per account; revoke, then create, to rotate. MCP config: MCP server docs, user mode.
  3. Only if the agent should withdraw: start it and ask it for its signing address (the mutex_signer_addresstool; the key is generated on the agent's machine on first run). Paste that under Agent signing key, pick 30 or 90 days, and Authorize: your linked wallet signs the delegation.
  4. The agent now trades as you, and withdraws to your linked wallets if you did step 3.
Control

Revoke

Settings > Agents lists the agent key and every signing key with a Revoke button. Revoking the agent key refuses its next request at once. Revoking a signing key takes one signature from a linked wallet and refuses its next withdrawal.

Turning Agent access off is faster and wider: every agent key is refused immediately. Flip it off first, revoke second.