A local daemon that gives AI agents secure, policy-controlled access to crypto wallets across EVM and Solana chains. Your keys, your machine, your rules.
8 EVM networks (Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche, BNB, HyperEVM) plus Solana. Native tokens, ERC-20/SPL, and NFTs.
Jupiter, 0x, LI.FI, Lido, Jito, Aave V3, Kamino, Pendle, Drift, D'CENT, Hyperliquid, Across Bridge, Polymarket. Swap, bridge, stake, lend, yield, perp, predict.
Session auth (JWT) + time-delay & owner approval + monitoring & kill switch. Default-deny policies for tokens, contracts, and spenders.
Model Context Protocol server for direct AI agent integration. Also provides REST API and TypeScript SDK. Agent self-discovery via connect-info.
Full-featured dashboard for wallet management, policy configuration, session control, DeFi positions, audit logs, and real-time notifications.
Account Abstraction with gas sponsorship. Lite/Full mode, CREATE2 address prediction, UserOp build/sign API. Pimlico and Alchemy providers.
Install the CLI globally via npm.
npm install -g @waiaas/cli
Launch the daemon with quickset for instant setup.
waiaas quickset
Copy the agent prompt from Admin UI and paste it into your AI agent.
open http://localhost:3100/admin
Add WAIaaS credentials to ~/.openclaw/openclaw.json:
Ask OpenClaw:
| Skill | Description |
|---|---|
| waiaas-setup | Zero-state daemon setup: install, initialize, start |
| waiaas-quickstart | End-to-end quickset: wallet, session, balance, transfer |
| waiaas-wallet | Wallet CRUD, assets, sessions, token registry |
| waiaas-transactions | All 9 transaction types |
| waiaas-policies | Policy engine: 12 policy types |
| waiaas-admin | Admin API: status, kill switch, notifications |
| waiaas-actions | DeFi actions through the pipeline |
| waiaas-x402 | x402 auto-payment protocol |
Installs 8 skill files to .claude/skills/ in your project directory.
Add WAIaaS credentials to .claude/settings.json:
Ask Claude Code:
You can also use slash commands like /waiaas-quickstart, /waiaas-wallet, or just ask naturally.
Copy the generated mcpServers config to your client's settings file:
| Client | Settings File |
|---|---|
| Claude Code | .claude/settings.json (project) or ~/.claude/settings.json (global) |
| Cursor | .cursor/mcp.json |
| Claude Desktop | ~/Library/Application Support/Claude/claude_desktop_config.json |
The MCP server includes a connect_info tool. Call it first to discover wallets, policies, and all 18 MCP tools.
| Skills | MCP | |
|---|---|---|
| Setup | npx @waiaas/skills <client> | waiaas mcp setup |
| How it works | Agent reads docs, uses curl | Agent calls MCP tools directly |
| Auth | Manual headers per request | Automatic (token file) |
| Best for | Learning the API, custom flows | Production, automated agents |
WAIaaS (Wallet AI as a Service) is a self-hosted daemon that gives AI agents secure, policy-controlled access to crypto wallets across EVM and Solana chains. It runs locally on your machine — your keys, your rules.
Install via npm with npm install -g @waiaas/cli, then run waiaas quickset for instant setup. Alternatively, use Docker: docker run -d -p 127.0.0.1:3100:3100 -v waiaas-data:/data -e WAIAAS_AUTO_PROVISION=true waiaas/daemon.
WAIaaS supports 8 EVM networks (Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche, BNB Chain, HyperEVM) and Solana. It handles native tokens, ERC-20/SPL tokens, and NFTs (ERC-721, ERC-1155, Metaplex).
AI agents can connect via three interfaces: MCP (Model Context Protocol) for direct tool integration, REST API for HTTP-based access, or the TypeScript SDK (@waiaas/sdk) for programmatic control. Skill files are also available for Claude Code and OpenClaw.
WAIaaS uses a 3-layer security model: session authentication (JWT), time-delay and owner approval (via WalletConnect, Telegram, or Wallet SDK), and monitoring with kill switch. It enforces default-deny policies for tokens, contracts, and spenders. Private keys are encrypted at rest with Argon2id key derivation.
Run docker run -d -p 127.0.0.1:3100:3100 -v waiaas-data:/data -e WAIAAS_AUTO_PROVISION=true waiaas/daemon. This starts the daemon on port 3100 with persistent storage. Access the Admin UI at http://localhost:3100/admin to manage wallets and configure policies.
WAIaaS requires Node.js 22+ (for npm install) or Docker (for containerized deployment). It runs on macOS, Linux, and Windows. The daemon uses SQLite for local storage, so no external database is needed.
Initial configuration is done via config.toml for infrastructure settings (port, host, RPC URLs). Runtime settings are managed through the Admin Settings UI or the REST API (PUT /v1/admin/settings), which supports hot-reload without daemon restart.
Private keys are encrypted at rest using sodium-native (libsodium) with Argon2id key derivation from the master password. Keys are stored in a local SQLite database on your machine. The master password never leaves your device.
WAIaaS enforces a default-deny security model. AI agents cannot interact with tokens, contracts, or spenders unless explicitly whitelisted via ALLOWED_TOKENS, CONTRACT_WHITELIST, and APPROVED_SPENDERS policies.
WAIaaS supports three owner approval channels: WalletConnect (sign with your mobile wallet), Telegram Bot (approve via chat), and Wallet SDK (custom approval flows). When a transaction exceeds policy thresholds, the daemon sends an approval request to the configured channel.
Yes. WAIaaS integrates with Jupiter (Solana DEX), 0x (EVM DEX aggregator), and D'CENT Swap for decentralized token trading. Agents can execute swaps with slippage protection through the policy-controlled pipeline.
Yes. WAIaaS integrates with Aave V3 (EVM lending across Ethereum, Polygon, Arbitrum, Optimism, Base) and Kamino (Solana lending). AI agents can supply collateral, borrow assets, repay loans, and monitor positions.
Yes. WAIaaS integrates with LI.FI and Across Bridge for cross-chain token transfers between EVM networks and Solana with route optimization and fee comparison.
The @waiaas/sdk package is a TypeScript SDK that wraps the WAIaaS REST API. It provides typed methods for wallet management, transaction submission, policy configuration, and DeFi operations.
WAIaaS includes a built-in MCP (Model Context Protocol) server with 42 tools. AI agents like Claude can directly call wallet operations through MCP without HTTP requests. The connect_info tool provides self-discovery of available wallets and capabilities.
Yes. Install skills with npx @waiaas/skills claude-code which adds 8 skill files to .claude/skills/. Alternatively, use MCP integration by adding the WAIaaS MCP server to .claude/settings.json.
Every transaction passes through 6 stages: Validate (check parameters), Policy (enforce limits), Delay/Approval (optional owner approval), Sign (cryptographic signature), Broadcast (submit to blockchain), and Confirm (wait for on-chain confirmation).
Yes. WAIaaS supports ERC-4337 Smart Accounts in Lite (EOA + UserOp wrapping) and Full (CREATE2-deployed smart contract) modes. Features include gas sponsorship via paymasters and bundler integration (Pimlico, Alchemy).
The Admin Web UI is a browser-based dashboard at /admin for managing your WAIaaS daemon. It provides wallet management, policy configuration, session control, DeFi position monitoring, audit logs, and notification settings.