FDX is a command-line interface to the Finance District MCP wallet server. It gives AI agents crypto wallet capabilities — hold, send, swap, and earn yield on assets across multiple chains — without managing private keys.
FDX is built for advanced users and environments where agents have access to CLI tooling and bash — Docker containers, CI pipelines, remote servers, and scripted automation. Agents invoke fdx wallet <method> or fdx prism <method> from the command line and parse JSON output. FDX also powers the Agent Wallet CLI Skills, which plug it directly into OpenClaw, GitHub Copilot, and 40+ other agentic platforms.
- No Key Management — Email OTP authentication. No seed phrases. No private key files.
- Agent-Native — Structured JSON input/output designed for tool-calling agents.
- Multi-Chain — Ethereum, BSC, Arbitrum, Base, Solana. One wallet, all chains.
- DeFi Enabled — Transfer, swap, and earn yield through integrated DeFi protocols.
For full documentation, architecture details, and development instructions,
see the FDX GitHub
repository. Quick Start
Install globally:
npm install -g @financedistrict/fdx
fdx register --email you@example.com
fdx verify --code 12345678
fdx login --email you@example.com
fdx verify --code 12345678
Authentication
FDX uses email one-time passcode (OTP) authentication via Microsoft Entra External ID. No browser is required — the entire flow runs headlessly, making it ideal for autonomous agents, Docker containers, CI pipelines, and remote servers.
Register (first time)
fdx register --email you@example.com
# Check your inbox for an 8-digit OTP
fdx verify --code 12345678
Login (returning users)
fdx login --email you@example.com
# Check your inbox for an 8-digit OTP
fdx verify --code 12345678
Token storage
Tokens are stored in the OS credential store where available:
| Platform | Backend |
|---|
| macOS | Keychain (security CLI) |
| Linux | libsecret (secret-tool CLI) |
| Windows | DPAPI (encrypted file in ~/.fdx/) |
~/.fdx/auth.json with a SecurityWarning emitted. Tokens are refreshed automatically using the stored refresh token.
Logging out
Removes stored tokens from the OS credential store and clears ~/.fdx/auth.json.
Usage
Wallet tools use the fdx wallet subcommand and Prism tools use fdx prism:
# Check wallet overview
fdx wallet getWalletOverview --chainKey ethereum
# Send tokens
fdx wallet transferTokens --chainKey ethereum --toAddress 0xABC... --amount 0.1 --asset USDC
# Discover yield strategies
fdx wallet discoverYieldStrategies --chainKey base
# List Prism payments
fdx prism listPayments
fdx wallet getMyInfo | jq '.email'
fdx wallet without arguments to see all available wallet methods. Run fdx services to see all available services.
fdx call <method> was deprecated in v0.4.0 and now exits with an error. Use fdx wallet <method> for wallet tools or fdx prism <method> for Prism tools.
Services
# List all available MCP services and their URLs
fdx services
| Service | Subcommand | URL | Description |
|---|
wallet | fdx wallet | https://mcp.fd.xyz | Wallet tools (DeFi, transfers, X402) |
prism | fdx prism | https://prism-mcp.fd.xyz | Prism tools (payments, settlements) |
Using FDX with Agent Frameworks
FDX is designed to work with agent frameworks where the agent can execute shell commands.
Most agent frameworks let you define custom tools. Wrap FDX as a shell tool:
import subprocess
import json
def wallet_command(method: str, **kwargs) -> dict:
"""Execute an FDX wallet command and return JSON result."""
args = ["fdx", "wallet", method]
for key, value in kwargs.items():
args.extend([f"--{key}", str(value)])
result = subprocess.run(args, capture_output=True, text=True)
return json.loads(result.stdout)
# Check wallet overview
overview = wallet_command("getWalletOverview", chainKey="ethereum")
# Transfer tokens
wallet_command("transferTokens", chainKey="ethereum", toAddress="0x1234...5678", amount="5", asset="USDC")
Script-based automation
#!/bin/bash
BALANCE=$(fdx wallet getWalletOverview --chainKey base | jq -r '.balances[0].amount')
echo "Current balance: $BALANCE"
FDX vs. MCP Server
FDX and MCP server connect to the same backend and offer the same capabilities:
| Aspect | MCP Server | FDX CLI |
|---|
| Interface | MCP protocol (tool calls) | Terminal commands (fdx wallet / fdx prism) |
| Connection | MCP client → server | FDX → MCP client → server |
| Best for | AI agents in MCP clients | Scripts, automation, agent frameworks with shell access |
| Login | Config file in MCP client | npm install -g + fdx login |
| Auth | OAuth PKCE | Email OTP (Microsoft Entra External ID) |
| Output | MCP tool responses | JSON |
