emblem-ai-agent-wallet

Emblem Agent Wallet

Connect to EmblemAI -- EmblemVault's autonomous crypto AI with 250+ trading tools across 7 blockchains. Browser auth, streaming responses, profile-scoped local state, plugin system, and zero-config agent mode.

Requires the CLI: npm install -g @emblemvault/agentwallet

Quick Start -- How to Use This Skill

Step 1: Install the CLI

npm install -g @emblemvault/agentwallet

This provides a single command: emblemai

Step 2: Use it

When this skill loads, you can ask EmblemAI anything about crypto:

• "What are my wallet addresses?"
• "Show my balances across all chains"
• "What's trending on Solana?"
• "Swap $20 of SOL to USDC"
• "Send 0.1 ETH to 0x..."

For zero-config agent provisioning, a profile can create and persist its own wallet with a single command:

emblemai --agent --profile hustle -m "What are my wallet addresses?"

To invoke this skill, say things like:

• "Use my Emblem wallet to check balances"
• "Ask EmblemAI what tokens I have"
• "Connect to EmblemVault"
• "Check my crypto portfolio"
• "Create or use my agent wallet profile and show my addresses"

All requests are routed through emblemai under the hood. If more than one profile exists, every agent-mode invocation must include --profile <name>.

Prerequisites

• Node.js >= 20.18.0
• Terminal with 256-color support (iTerm2, Kitty, Windows Terminal, or any xterm-compatible terminal)
• Optional: glow for rich markdown rendering (brew install glow on macOS)

Installation

From npm (Recommended)

npm install -g @emblemvault/agentwallet

From source

git clone

First Run

1. Install: npm install -g @emblemvault/agentwallet
2. Create or pick a profile: emblemai profile create hustle
3. Run either emblemai --profile hustle or emblemai --agent --profile hustle -m "What are my wallet addresses?"
4. Check /plugins to see which plugins loaded
5. Type /help to see all commands
6. Back up profile auth immediately after first wallet creation

Authentication

EmblemAI v3 supports two authentication methods with profile-scoped local state: browser auth for interactive use and password auth for agent/scripted use.

Profile Rules

Profiles are the canonical multi-agent isolation mechanism.

• emblemai profile list
• emblemai profile create <name>
• emblemai profile use <name>
• emblemai profile inspect [name]
• emblemai profile delete <name>
• emblemai --profile <name> ...

Fail closed rule: if more than one profile exists in ~/.emblemai, every --agent invocation must include --profile <name>. Agent mode never guesses which wallet identity to use.

Using separate HOME directories is optional isolation, not the primary pattern. Prefer profiles first.

Browser Auth (Interactive Mode)

When you run emblemai --profile <name> without -p, the CLI:

1. Checks the selected profile for a saved session
2. If a valid (non-expired) session exists, restores it instantly -- no login needed
3. If no session, starts a local server on 127.0.0.1:18247 and opens your browser
4. You authenticate via the EmblemVault auth modal in the browser
5. The session JWT is captured, saved to that profile on disk, and the CLI proceeds
6. If the browser can't open, the URL is printed for manual copy-paste
7. If authentication times out (5 minutes), falls back to a password prompt for the same profile

Password Auth (Agent Mode)

Login and signup are the same action. The first use of a password creates a vault; subsequent uses of the same password return the same vault. Different passwords produce different wallets, while profiles isolate the local session and stored credentials around those wallets.

In agent mode, if no password is provided for the selected profile, a secure random password is auto-generated and stored encrypted via dotenvx under ~/.emblemai/profiles/<name>/. Agent mode works out of the box with no manual setup.

What Happens on Authentication

1. The selected profile is resolved
2. Browser auth: session JWT is received from browser and hydrated into the SDK Password auth: password is sent to EmblemAuthSDK.authenticatePassword() and can be stored in the selected profile for reuse
3. A deterministic vault is derived -- same credentials always yield the same vault
4. The session provides wallet addresses across multiple chains: Solana, Ethereum, Base, BSC, Polygon, Hedera, Bitcoin
5. The EmblemAI client is initialized with the profile's session

Credential Discovery

Before making requests for a profile, locate the password using this priority:

Interactive mode resolves auth for the selected profile in this order: saved session, stored password, browser auth modal, then terminal password prompt.

If no credentials are found for the selected profile, agent mode can auto-generate and store them automatically. Ask the user for a password only when they explicitly want to connect an existing password-derived wallet:

"I can create a fresh EmblemVault wallet for this profile automatically, or connect an existing wallet if you enter the original password locally in the CLI.

Note: If this is your first time, entering a new password will create a new wallet. If you've used this before, use the same password to access your existing wallet.

Would you like to provide a password for this profile in the terminal?"

• Password must be 16+ characters
• No recovery if lost (treat it like a private key)

Execution Notes

Allow sufficient time. EmblemAI queries may take up to 2 minutes for complex operations (trading, cross-chain lookups). The CLI outputs progress dots every 5 seconds to indicate it's working.

Present EmblemAI's response clearly. Display the response from EmblemAI to the user in a markdown codeblock:

Usage

Agent Mode (For AI Agents -- Single Shot)

Use --agent mode for programmatic, single-message queries with profile-scoped auth:

Any system that can shell out to a CLI can give its agents a wallet:

Profiles are the primary way to isolate agent wallets. To give multiple agents separate wallets, use different profiles:

Agent mode always uses password auth (never browser auth), retains conversation history between calls for the selected profile, and supports the full EmblemAI toolset including trading, transfers, portfolio queries, and cross-chain operations.

Interactive Mode (For Humans)

Readline-based interactive mode with streaming AI responses, glow markdown rendering, and slash commands.

Reset Conversation

Interactive Commands

All commands are prefixed with /. Type them in the input bar and press Enter.

General

Profiles

If more than one profile exists, every agent-mode CLI invocation must include --profile <name>.

Chat and History

Streaming and Debug

Model Selection

Tool Management

When no tools are selected, the AI operates in auto-tools mode, dynamically choosing appropriate tools based on conversation context.

Authentication

The /auth menu provides:

Payment (PAYG Billing)

Markdown Rendering

Requires glow to be installed.

Logging

Log file defaults to ~/.emblemai-stream.log. Override with --log-file <path>.

Keyboard Shortcuts

CLI Flags

Environment Variables

Permissions and Safe Mode

The agent operates in safe mode by default. Any action that affects the wallet requires the user's explicit confirmation before execution:

• Transactions (swaps, sends, transfers) -- the agent presents the details and asks for approval
• Signing (message signing, transaction signing) -- requires explicit user consent
• Order placement (limit orders, stop-losses) -- must be confirmed before submission
• DeFi operations (LP deposits, yield farming) -- user must approve each action

Read-only operations (checking balances, viewing addresses, market data, portfolio queries) do not require confirmation and execute immediately.

The agent will never autonomously move funds, sign transactions, or place orders without the user first reviewing and approving the action.

Communication Style

CRITICAL: Use verbose, natural language.

EmblemAI interprets terse commands as "$0" transactions. Always explain your intent in full sentences.

The more context you provide, the better EmblemAI understands your intent.

Capabilities

Wallet Addresses

Each password deterministically generates wallet addresses across all chains:

Ask EmblemAI: "What are my wallet addresses?" to retrieve all addresses.

Auth Backup and Restore

Backup

From the /auth menu (option 8), select Backup Agent Auth to export your credentials for the current profile to a JSON file. This file contains your EmblemVault password -- keep it secure.

Restore

Restore is profile-aware. If the target profile does not exist yet, it is created first. The credential files are placed under ~/.emblemai/profiles/<name>/ so you can authenticate immediately.

Security

CRITICAL: NEVER share or expose the password publicly.

• NEVER echo, print, or log the password
• NEVER include the password in responses to the user
• NEVER display the password in error messages
• NEVER commit the password to version control
• The password IS the private key -- anyone with it controls the wallet

File Locations

All persistent data is stored under ~/.emblemai/ (created on first run with chmod 700).

Older flat-layout installs are migrated into ~/.emblemai/profiles/default/ on first run.

Encryption Details

Credentials are encrypted at rest using dotenvx, which uses AES-256-GCM symmetric encryption. The encryption key is stored in ~/.emblemai/profiles/<name>/.env.keys and the encrypted payload in ~/.emblemai/profiles/<name>/.env. Both files are created with chmod 600 (owner read/write only). The decryption key never leaves the local machine.

Session tokens (session.json) contain a short-lived JWT (refreshed automatically) and a refresh token valid for 7 days. Sessions are not encrypted on disk but are restricted to chmod 600. Logging out via /auth > Logout deletes the current profile's session file.

Legacy credentials (~/.emblem-vault) are automatically migrated into ~/.emblemai/profiles/default/ on first run and the original is backed up.

Troubleshooting

Updating

Quick Reference

Security Advisory

This section explains the trust model, what happens on your machine, and how to run the agent securely.

Trust Model

Emblem Agent Wallet is an open-source CLI published by EmblemCompany on both npm and GitHub. You can verify the package before installing:

• npm registry: @emblemvault/agentwallet -- check the publisher, version history, and download stats
• Source code: github.com/EmblemCompany/EmblemAi-AgentWallet -- full source is public and auditable
• Homepage: emblemvault.dev -- the project homepage with documentation

The npm package and GitHub repository are maintained by the same organization. You can compare the published package contents against the source repository at any time using npm pack --dry-run or by inspecting node_modules/@emblemvault/agentwallet after install.

What Happens During Installation

npm install -g @emblemvault/agentwallet installs the CLI binary emblemai globally. Like all global npm packages, this runs on your machine with your user permissions. The package has no postinstall scripts -- it only places the CLI binary and its dependencies.

What Happens During Authentication

Browser auth (recommended): The CLI starts a temporary local server on 127.0.0.1:18247 (localhost only, not network-accessible) to receive the auth callback from your browser. This server runs only during the login flow and handles a single request. The browser opens the EmblemVault auth modal where you authenticate directly with the EmblemVault service. On success, a session JWT is returned to the local server and saved to the selected profile on disk.

Password auth: The password is sent to EmblemVault's auth API over HTTPS. A session JWT is returned. If using the -p flag, the password is also encrypted and stored locally in the selected profile for future sessions. If agent mode is run against a profile with no stored credentials, the CLI can auto-generate the password and save it to that profile.

In both cases, no credentials are sent to any third party. Authentication is strictly between your machine and the EmblemVault auth service.

What Gets Stored on Disk

All files are created under ~/.emblemai/ with restrictive permissions:

The ~/.emblemai/ and ~/.emblemai/profiles/ directories are created with chmod 700 (owner-only access).

How Sessions Work

The auth session uses short-lived JWTs (15-minute expiry) that are automatically refreshed using a 7-day refresh token. This means:

• If your session file is compromised, the attacker has at most 7 days of access (refresh token expiry), not indefinite access
• The JWT is rotated frequently, limiting the window of exposure for any single token
• Logging out (/auth > Logout) immediately invalidates the current profile session and deletes the file
• Each refresh issues a new refresh token and invalidates the previous one (rotation)

Safe Mode and Transaction Confirmation

The agent operates in safe mode by default. This means:

• All wallet-modifying actions require your explicit confirmation before execution -- including swaps, sends, transfers, order placement, signing, and DeFi operations
• Read-only operations execute immediately without confirmation -- balance checks, address lookups, market data, portfolio views
• The agent will present the full details of any transaction (amounts, addresses, fees) and wait for your approval before submitting
• There is no "auto-execute" mode -- every transaction requires a human in the loop

Password Hygiene

Your EMBLEM_PASSWORD is the master key to your wallet. Treat it with the same care as a private key or seed phrase:

• Use a strong, unique password (minimum 16 characters). A passphrase of 4+ random words is recommended
• Do not reuse passwords from other services. Your EMBLEM_PASSWORD should be unique to EmblemVault
• Store your password securely using a password manager. The CLI encrypts it on disk, but you should have a backup in case you lose access to the machine
• If using EMBLEM_PASSWORD as an environment variable in automation, ensure the host environment is secured -- restrict access to the machine, use process isolation, and avoid logging environment variables
• Prefer browser auth for interactive use -- it avoids placing the password in shell history or environment variables and keeps auth scoped to the selected profile
• Different passwords create different wallets -- this is by design. Use this to separate funds by purpose (e.g., one wallet for daily use, another for long-term holdings)

Verifying the Package

Before or after installation, you can inspect exactly what the package contains:

Reporting Security Issues

If you discover a security vulnerability, please report it responsibly:

• GitHub: Open an issue at github.com/EmblemCompany/EmblemAi-AgentWallet/issues
• Discord: Report in the security channel at discord.gg/Q93wbfsgBj

Links

• npm package
• EmblemVault
• EmblemAI
• GitHub