Wallet MCP tools
The wallet MCP is the server an AI agent talks to in order to pay: it checks the wallet, pays x402 services, transfers USDC and waits for a human approval. This page lists every tool it exposes to the agent. It is the agent's surface; the tools a signed-in person's assistant uses to create and configure wallets are on the Admin tools page.
How to read this page
- Tool is the name the agent calls.
- What it does is the first sentence of the description the server gives the agent. The agent reads the full text; the first sentence is enough to tell the tools apart.
- Inputs lists the arguments of the tool. An input marked optional can be left out.
- A payment tool is not a bypass: Keyban evaluates every payment against the wallet policy first, and a refusal carries a
policy/…reason, listed on the Refusal reasons page.
Three things change what an agent sees:
- Until the wallet is configured, the server exposes only
get_wallet_instructionsandsetup_instructions, which explains what is missing. The other tools appear once the configuration is complete. - Some tools exist only for the approval cards the MCP shows to the user (the payment card and the mission card). They are called by the card, not by the agent, and are not listed.
- The mission tools,
wait_for_mission_run,publish_missionand the…_in_missionpayment tools belong to missions. The…_in_missiontools pay inside a mission run: without a run, they have nothing to pay in.
Tools
| Tool | What it does | Inputs |
|---|---|---|
api_status | Check the Keyban API health status. | none |
balance | Show the current account balance, led by its value in the application's preferred fiat currency (quoted from the Keyban backend rate oracle); the USDC amount is complementary. | none |
cancel_intent | Withdraw your own in-flight policy intent — it moves to abandoned, releasing any budget it holds. | intentId |
discover_x402_services | Discover online services that accept x402 payments, from the Keyban x402 service directory (mirrored from Coinbase and Orthogonal). | query (optional), network (optional), tag (optional), limit (optional) |
expense_stats | Read-only spend summary for the application's agent wallets over a period, this month by default: total spent, transaction count, average ticket, display currency and excluded assets. | applicationId (optional), agentId (optional), operatorId (optional), ownerId (optional), period (optional) |
get_account_info | Get the current account address, public key, and network, plus the Keyban welcome offer when one is active: while it lasts, tell the user the offer covers payments up to the remaining amount, not that the wallet needs funding. | none |
get_wallet_instructions | Return the guide to follow with this server (the keyban-agent-wallet skill): funding the wallet, paying x402 APIs, transferring USDC, waiting for a human approval, reading a policy refusal. | none |
list_expense_transactions | Read-only aggregated on-chain transfers across the application's agent wallets, newest first, offset-paginated. | applicationId (optional), agentId (optional), operatorId (optional), ownerId (optional), currentPage (optional), pageSize (optional) |
list_my_wallets | List the wallets kept on this machine (by keyban wallet import): id, name, address, network, funding, which one is current (driven here) and which one is the default (driven by the CLI and every later start). | none |
publish_mission | Checks that the open draft of a mission can be published and shows it to the user with the page where they publish it in the Keyban dashboard. | mission |
setup_instructions | This Keyban agent wallet has no wallet to drive yet, so none of its usual tools are available. | none |
sign_message | Sign an arbitrary message with the account key (EIP-191 personal sign for EVM). | message |
transfer_usdc | Transfer USDC (ERC-20) from the wallet the user provisioned for this agent to an address. | to, value |
transfer_usdc_in_mission | transfer_usdc for a transfer of a mission run (missionRunId required), once the run is active. | to, value, missionRunId |
use_wallet | Drive another kept wallet from now on, in this server only unless global. | wallet, global (optional) |
wait_for_intent | Block until something happens to the wallet's human-approval queue, then return the current picture. | timeoutMs (optional) |
wait_for_mission_run | Waits for a wallet operator to decide on a mission trial or run that waits for approval. | runId, timeoutMs (optional) |
x402_info | Check whether a URL supports the x402 payment protocol without initiating any payment. | url, method (optional), headers (optional), body (optional), timeoutMs (optional) |
x402_pay | Fetch an x402-protected HTTP resource, automatically handling payment. | url, method (optional), headers (optional), body (optional), maxAmount (optional), intentId (optional) |
x402_pay_in_mission | x402_pay for a payment of a mission run (missionRunId required), once the run is active. | url, method (optional), headers (optional), body (optional), maxAmount (optional), intentId (optional), missionRunId |
Mission tools, served to the wallet MCP by the Keyban API:
| Tool | Type | What it does |
|---|---|---|
abandon_mission_run | Tool | Abandon a pending mission run |
complete_mission_run | Tool | Complete a mission run |
create_mission | Tool | Create a mission |
discard_mission_draft | Tool | Discard the open draft |
get_mission | Resource | Get a mission |
get_mission_run | Resource | Get a mission run |
list_mission_run_payments | Resource | List the payments of a mission run |
list_mission_runs | Resource | List the mission runs of a wallet |
list_missions | Resource | List missions |
list_runs_of_mission | Resource | List the runs of a mission |
log_mission_progress | Tool | Log the progress of a mission run |
request_mission_trial | Tool | Request a trial of the draft |
start_mission_run | Tool | Start a mission run |
update_mission | Tool | Update a mission |
Missions
The mission tools in the second table are served by the Keyban API and added to the wallet MCP when the API offers them. wait_for_mission_run and the two payment tools x402_pay_in_mission and transfer_usdc_in_mission belong to the same cycle and are listed in the first table. A mission is an envelope of money a human validates for a task. The agent pays inside a run of that mission with x402_pay_in_mission or transfer_usdc_in_mission, which take the run id as missionRunId; x402_pay and transfer_usdc refuse it. See Missions for the whole cycle.