Keyban Agent Wallet runs on your own machine — the client starts it, so there is no endpoint to ping. 87 installs a week from npm.
Give an AI agent its own blockchain wallet: balances, USDC transfers, x402 payments under policy.
Nothing serious here today
Today is the operative word: we check Keyban Agent Wallet every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add agent-wallet -e 'KEYBAN_API_KEY=<KEYBAN_API_KEY>' -e 'KEYBAN_APP_ID=<KEYBAN_APP_ID>' -e 'KEYBAN_INVITE_KEY=<KEYBAN_INVITE_KEY>' -e 'KEYBAN_WALLET_ADDRESS=<KEYBAN_WALLET_ADDRESS>' -e 'KEYBAN_NETWORK=<KEYBAN_NETWORK>' -- npx -y @keyban/cli{
"mcpServers": {
"agent-wallet": {
"command": "npx",
"args": [
"-y",
"@keyban/cli"
],
"env": {
"KEYBAN_API_KEY": "<KEYBAN_API_KEY>",
"KEYBAN_APP_ID": "<KEYBAN_APP_ID>",
"KEYBAN_INVITE_KEY": "<KEYBAN_INVITE_KEY>",
"KEYBAN_NETWORK": "<KEYBAN_NETWORK>",
"KEYBAN_WALLET_ADDRESS": "<KEYBAN_WALLET_ADDRESS>"
}
}
}
}[mcp_servers.agent-wallet]
command = "npx"
args = ["-y", "@keyban/cli"]
env = { KEYBAN_API_KEY = "<KEYBAN_API_KEY>", KEYBAN_APP_ID = "<KEYBAN_APP_ID>", KEYBAN_INVITE_KEY = "<KEYBAN_INVITE_KEY>", KEYBAN_WALLET_ADDRESS = "<KEYBAN_WALLET_ADDRESS>", KEYBAN_NETWORK = "<KEYBAN_NETWORK>" }{
"mcpServers": {
"agent-wallet": {
"command": "npx",
"args": [
"-y",
"@keyban/cli"
],
"env": {
"KEYBAN_API_KEY": "<KEYBAN_API_KEY>",
"KEYBAN_APP_ID": "<KEYBAN_APP_ID>",
"KEYBAN_INVITE_KEY": "<KEYBAN_INVITE_KEY>",
"KEYBAN_NETWORK": "<KEYBAN_NETWORK>",
"KEYBAN_WALLET_ADDRESS": "<KEYBAN_WALLET_ADDRESS>"
}
}
}
}{
"servers": {
"agent-wallet": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@keyban/cli"
],
"env": {
"KEYBAN_API_KEY": "<KEYBAN_API_KEY>",
"KEYBAN_APP_ID": "<KEYBAN_APP_ID>",
"KEYBAN_INVITE_KEY": "<KEYBAN_INVITE_KEY>",
"KEYBAN_NETWORK": "<KEYBAN_NETWORK>",
"KEYBAN_WALLET_ADDRESS": "<KEYBAN_WALLET_ADDRESS>"
}
}
}
}Put your own values in place of
<KEYBAN_API_KEY> (Keyban API key of the application the wallet belongs to. Never exposed to the model), <KEYBAN_APP_ID> (Identifier of the Keyban application), <KEYBAN_INVITE_KEY> (One-shot ECDSA private key (0x + 64 hex) authorizing the first-boot registration of this client as a FROST signer of the wallet), <KEYBAN_WALLET_ADDRESS> (Address of the deployed SchnorrAccount this server drives (0x + 40 hex)), <KEYBAN_NETWORK> (Blockchain network the wallet operates on, for example base or xdc).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
KEYBAN_BASE_URL (Base URL of the Keyban backend. Accepts a full URL, or one of the environment aliases dev, testing, staging, prod and sandbox), KEYBAN_DKG_BLOB (Optional pre-generated FROST client share, base64-encoded JSON. Used by hosted runtimes with no OS keyring; it does not replace the invite key), MCP_LOG_FILE (Path the server writes its log to), MCP_LOG_LEVEL (Log verbosity).
Alternatives to Keyban Agent Wallet
same job, measured the same wayCircle Agent Stack for AI agents: USDC wallets, spend policies, transfers, and x402 nanopayments.
Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.
Local Ethereum wallet for AI agents on Base and Arc: balances, x402 payments. Keys stay local.
x402 micropayments for AI agents — credits-based, no wallets, no blockchain.
Pay-per-use web extract, token prices, and wallet balances via x402 USDC micropayments.
Crypto wallet for AI agents: balances, payments, swaps and trading with owner controls.
Payment layer for AI agents. Send USDC, manage escrows on Base blockchain.
Secure USDC payments for AI agents on Base blockchain with budget controls and instant settlement.
Keyban Agent Wallet — questions
Answers built from our own checks of this server.