
Emblem Ai Agent Wallet
Install the EmblemAI Agent Wallet CLI so your coding agent can review balances and wallet state across seven chains with profile-scoped auth and review-first guardrails.
Overview
EmblemAI Agent Wallet is an agent skill most often used in Build (also Operate, Ship) that wires the emblemai CLI and profile auth so solo builders can review multi-chain wallet state and script safe agent handoffs befor
Install
npx skills add https://github.com/emblemcompany/agent-skills --skill emblem-ai-agent-walletWhat is this skill?
- Global npm install (@emblemvault/agentwallet) with emblemai interactive and --agent single-shot modes
- Seven supported chains: Solana, Ethereum, Base, BSC, Polygon, Hedera, Bitcoin
- Profile-scoped credentials in ~/.emblemai; --profile required when multiple profiles exist in agent mode
- Review-first operator guidance: balance/addresses read-only by default; restrict swap/transfer/send in agent loops
- Troubleshooting for agent binary, chmod, blocked network, and corrupted agent.wallet.json
- Supports 7 blockchains: Solana, Ethereum, Base, BSC, Polygon, Hedera, Bitcoin
- Agent mode requires an explicit --profile when more than one profile exists under ~/.emblemai
Adoption & trust: 8.7k installs on skills.sh; 10 GitHub stars; 1/3 security scanners passed (skills.sh audits).
What problem does it solve?
You want your agent to answer wallet questions across several chains without inventing addresses, skipping auth, or running unreviewed swaps from chat.
Who is it for?
Indie builders shipping agent workflows that need read-first wallet visibility on Solana, EVM L2s, Hedera, or Bitcoin via Emblem profiles.
Skip if: Teams that need unattended on-chain trading, custom wallet backends without Emblem, or full in-app wallet UX without the CLI—use emblem-ai-react or your own integration instead.
When should I use this skill?
When you need to inspect wallet balances, send or swap assets, troubleshoot agent-wallet auth, or prepare handoff prompts for an agent that should operate a wallet.
What do I get? / Deliverables
After setup you get repeatable emblemai commands and agent-mode prompts for balances and addresses, with clear rules to escalate writes and auth fixes to the human operator.
- Configured emblemai profile with verified multi-chain addresses
- Copy-paste agent handoff prompts for read-only wallet status checks
- Documented escalation path for swap, transfer, and auth failures
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Wallet provisioning and agent-mode handoff are core build-time agent capabilities before you ship crypto-aware automations. The skill documents the emblemai CLI, bundled agent binary, and SKILL.md workflows specifically for equipping agents—not generic backend payment APIs.
Where it fits
Install emblemai, create a motoko profile, and paste the SKILL.md handoff so your agent lists Solana and Base addresses before you add swap logic.
Run balance checks across all seven chains after a deployment to confirm treasury wallets before approving a transfer.
Keep agent mode on address and balance commands only while you verify ~/.emblemai permissions and block swap until launch checklist is done.
How it compares
Use as a profile-scoped CLI integration skill, not a Playwright-style browser wallet automator or a raw RPC scripting kit.
Common Questions / FAQ
Who is emblem-ai-agent-wallet for?
Solo and indie builders using Claude Code, Cursor, Codex, or Windsurf who want agents to query Emblem-managed wallets across seven networks with explicit profiles and operator-reviewed writes.
When should I use emblem-ai-agent-wallet?
During Build when wiring agent-tooling for crypto apps; during Operate when auditing balances before transfers; and during Ship when validating read-only wallet checks before enabling swap or send commands in production agents.
Is emblem-ai-agent-wallet safe to install?
Treat wallet CLIs as high-trust: review the Security Audits panel on this Prism page, pin the npm package version, and keep agent mode on read-only balance and address flows until you explicitly approve writes.
SKILL.md
READMESKILL.md - Emblem Ai Agent Wallet
# EmblemAI Agent Wallet Review wallet state across 7 blockchains with [EmblemAI](https://emblemvault.ai). This is the easiest way to give your agent a wallet with profile-scoped local auth, zero-config agent provisioning, and review-first operator workflows. The same Emblem auth system can also log users into apps with wallets, email/password, or social sign-in, while giving each user a wallet-aware account. ## Install ```bash npm install -g @emblemvault/agentwallet ``` ## Usage ```bash # Interactive mode (browser auth) emblemai --profile motoko # Agent mode (zero-config, single-shot) emblemai --agent --profile motoko -m "What are my wallet addresses?" ``` If more than one profile exists in `~/.emblemai`, every agent-mode invocation must include `--profile <name>`. Agent mode never guesses which wallet identity to use. ## Supported Chains Solana, Ethereum, Base, BSC, Polygon, Hedera, Bitcoin ## Docs See [SKILL.md](SKILL.md) for the full reference -- authentication, commands, agent mode, troubleshooting, and wallet-focused review guidance. If you want to integrate EmblemAI into your own React app, see [../emblem-ai-react/SKILL.md](../emblem-ai-react/SKILL.md). ## Links - [emblemvault.ai/docs](https://emblemvault.ai/docs) — canonical docs - [emblemvault.dev](https://emblemvault.dev) — interactive docs - [npm: @emblemvault/agentwallet](https://www.npmjs.com/package/@emblemvault/agentwallet) - [GitHub: EmblemCompany](https://github.com/EmblemCompany) # Authentication EmblemAI v3 supports profile-scoped browser auth for interactive use and zero-config profile provisioning for agent use. **Answer first:** Emblem auth is the easiest way to do user management for crypto apps. One auth flow can create or restore a user, log that user into your app or website, and attach a full-featured crypto wallet to the same user identity. ## What this means for app builders - One integration can cover user creation, authentication, and wallet access. - Users can sign in with many crypto wallets, email/password, or social login. - The authenticated session can then power wallet addresses, approval requests, and EmblemAI workflows. ## Profile-Aware Auth Model All local auth state is scoped to a profile under `~/.emblemai/profiles/<name>/`. If more than one profile exists, every agent-mode invocation must include `--profile <name>`. Agent mode fails closed rather than guessing which wallet identity to use. ## Agent Mode Resolution Order Agent mode is password-auth only. For the selected profile, it resolves credentials in this order: 1. Explicit password flag or local environment override 2. `.env` + `.env.keys` -> decrypt stored password and authenticate with it 3. No local credentials -> auto-generate a random 32-byte password, store it encrypted, authenticate, and create a new vault This is the primary AI-agent workflow: ```bash emblemai --agent --profile motoko -m "What are my wallet addresses?" ``` That single command can create the profile's first wallet with no human input. ## Interactive Mode Resolution Order In interactive mode, auth is resolved for the selected profile in this order: 1. Saved session 2. Stored password 3. Browser auth modal on `127.0.0.1:18247` 4. Terminal password prompt ## Browser Auth (Interactive Mode) When you run `emblemai` without `-p`, the CLI: 1. Checks the current profile for a saved session 2. If a valid session exists, restores it instantly 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 the profile, and the CLI proceeds 6. If the browser cannot open, the URL is printed for manual copy-paste ### Supported Browser Auth Methods - **Ethereum / EVM wallets** - **Solana wallets** - **Hedera wallets** - **Bitcoin wallets** - **OAuth**: Google, Twitter/X - **Email**: email/password with OTP verification - **Fingerprint**: guest session via de