WAIaaS Wallet — Self-Hosted Wallet for AI Agents

Your private keys should never live inside your agent process. If your agent is compromised, the attacker gets the keys. WAIaaS separates key custody into an isolated daemon with a policy engine that limits what any agent session can do.

What is WAIaaS?

WAIaaS (Wallet-as-a-Service for AI Agents) is a self-hosted local daemon that manages crypto wallets on behalf of AI agents. Unlike cloud wallet services (Coinbase CDP, Privy, Circle), WAIaaS runs entirely on your machine — no third-party API keys, no custodial risk.

Why use WAIaaS instead of raw keypairs?

Key features

• - Self-hosted: Local daemon, no third-party dependency
• Policy engine: Default-deny, token whitelist, per-token spending limits, cumulative caps
• Owner approval: High-value transactions require human signature (SIWE/SIWS/WalletConnect/D'CENT)
• Multi-chain: EVM (Ethereum, Base, Arbitrum, Polygon, Optimism) + Solana in one daemon
• 59+ MCP tools: Wallet ops, DeFi (swap/lend/stake/bridge/perp), NFT, x402, ERC-4337, ERC-8004
• Kill switch: Instantly freeze any wallet from Admin UI or API
• RPC proxy: Use as --rpc-url for Forge, Hardhat, ethers.js — every tx goes through policy engine

Quick Start

1. Install and start the daemon

CODEBLOCK0

The quickset command creates Solana + EVM wallets automatically, issues MCP session tokens, and outputs a ready-to-use MCP config snippet.

For testing, use waiaas quickset --mode testnet to create Solana Devnet + EVM Sepolia wallets.

2. Configure spending policies (recommended before connecting agents)

Set up spending limits and token whitelists via Admin UI at http://127.0.0.1:3100/admin. WAIaaS uses default-deny policy — agents cannot transact until policies are configured. This ensures human oversight before any agent gains financial capabilities.

3. Connect MCP server

Pass the session token via environment variable (do not hardcode tokens in config files):

CODEBLOCK1

Or auto-register with all wallets:

CODEBLOCK2

Security note: Store session tokens in environment variables or a secrets manager, not in plaintext config files. Session tokens are time-limited JWTs and can be revoked from the Admin UI at any time.

Available MCP Tools (59+)

Wallet Management

• - connect_info — Self-discovery: wallets, policies, capabilities. Call this first.
• INLINECODE5 — Wallet balance (native + USD)
• INLINECODE6 — Public address
• INLINECODE7 — All held assets (native + tokens)
• INLINECODE8 — Chain, address, environment, networks
• INLINECODE9 — Registered tokens for a network
• INLINECODE10 — Resolve CAIP-19 asset ID to metadata

Transactions

• - send_token — Send native (SOL/ETH) or tokens (ERC-20/SPL)
• INLINECODE12 — Call whitelisted smart contracts
• INLINECODE13 — Approve spender (requires APPROVED_SPENDERS policy)
• INLINECODE14 — Atomic multi-instruction transaction (Solana)
• INLINECODE15 — Sign without broadcasting
• INLINECODE16 — Personal sign or EIP-712 typed data
• INLINECODE17 — Dry-run with policy evaluation, no side effects
• INLINECODE18 — Encode EVM function call to hex

Transaction History

• - list_transactions — Outgoing transaction history (paginated)
• INLINECODE20 — Single transaction details
• INLINECODE21 — Incoming transfers (paginated, filterable)
• INLINECODE22 — Period-based incoming summary (daily/weekly/monthly)

DeFi (via Action Providers)

• - Swap: Jupiter (Solana), 0x (EVM), DCent Aggregator
• Bridge: LI.FI cross-chain, Across Protocol
• Lending: Aave V3 (EVM), Kamino (Solana)
• Staking: Lido (ETH), Jito (SOL)
• Yield: Pendle yield trading
• Perp: Drift (Solana), Hyperliquid (10 tools)
• Prediction: Polymarket (8 tools)

NFT

• - list_nfts — List owned NFTs (ERC-721/1155/Metaplex)
• INLINECODE24 — NFT metadata and attributes
• INLINECODE25 — Transfer NFT (requires approval tier)

Advanced

• - x402_fetch — HTTP 402 automatic payment
• INLINECODE27 / wc_status / wc_disconnect — WalletConnect pairing
• INLINECODE30 / sign_userop — ERC-4337 Account Abstraction
• INLINECODE32 — ERC-8004 Trustless Agent identity
• INLINECODE33 — ERC-8128 Signed HTTP Requests
• INLINECODE34 — EVM RPC proxy for Forge/Hardhat/ethers.js
• INLINECODE35 / list_offchain_actions — Credential vault and off-chain history

Example Workflows

Check balance and send tokens

CODEBLOCK3

DeFi operations

CODEBLOCK4

x402 automatic payment

CODEBLOCK5

Security Model

WAIaaS enforces a 3-layer security model:

1. 1. Session authentication: Agents use time-limited JWT session tokens. No master password exposure.
2. Policy engine: Default-deny. Configure ALLOWEDTOKENS, CONTRACTWHITELIST, SPENDINGLIMIT, RATELIMIT per wallet.
3. Owner approval + Kill switch: High-value transactions require human signature. Instant wallet freeze via Admin UI.

Transaction tiers:

• - AUTO_SIGN — Within policy limits, auto-approved
• INLINECODE38 — Delayed execution with notification
• INLINECODE39 — Requires owner wallet signature (SIWE/SIWS/WalletConnect)
• INLINECODE40 — Denied by policy

Links

• - Website: https://waiaas.ai
• GitHub: https://github.com/minhoyoo-iotrust/WAIaaS
• npm: @waiaas/cli, @waiaas/sdk, INLINECODE43
• Docker: INLINECODE44
• Admin UI: http://127.0.0.1:3100/admin (after daemon start)