> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.mitu.ai/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.mitu.ai/_mcp/server.

# Wallet tools

Wallet tools let an AI agent work with Agent Wallets belonging to the customer it is acting for. Once the AI client is connected as a customer, the agent can inspect available wallets, check balances, retrieve funding information and use an eligible wallet when a payment needs to be completed.

These tools are deliberately limited to the capabilities an agent needs for spending. They do not give the agent administrative control over the customer's wallets or funds, and they are only available in the context of the customer represented by the connection.

## `list_wallets`

Returns the Agent Wallets available to the connected customer. Use this when the agent needs to understand which wallets the customer has before checking a balance or deciding which wallet should be used for a payment.

This tool does not create wallets or make a wallet available to a customer who has not been issued one. If the connected customer has no Agent Wallets, the result should be treated as a valid account state rather than an error.

## `get_balance`

Returns the available balance for one or more of the connected customer's Agent Wallets.

| Parameter | Type     | Required | Description                                                                                       |
| --------- | -------- | -------- | ------------------------------------------------------------------------------------------------- |
| `wallet`  | `string` | No       | The wallet name to inspect. Omit it to retrieve balances across the customer's available wallets. |

When the customer has several wallets and no name is provided, the tool can return their balances together rather than forcing the agent to choose one. Reading balances does not move money, so showing the available balances does not create the same risk as selecting a wallet for payment.

## `get_address`

Returns the funding information for an Agent Wallet so the customer can add funds using a supported network.

| Parameter | Type     | Required    | Description                                                               |
| --------- | -------- | ----------- | ------------------------------------------------------------------------- |
| `wallet`  | `string` | Conditional | The wallet name. It can be omitted when the customer has only one wallet. |

The result associates each funding address with the network it supports. Base and Tempo can share an EVM address, while Solana uses a different address, so applications and agents should preserve the network label rather than presenting a funding address without context.

See [Funding](/platform/agent-wallets/funding) for supported funding methods and when deposited funds become available.

## `pay`

The `pay` tool lets an AI agent complete a payment using an Agent Wallet belonging to the connected customer. When the agent reaches a point in a larger workflow where payment is required, it receives a payment URL and passes that payment to Mitu. Mitu checks the selected wallet, available balance and applicable controls before completing the payment when it is permitted.

The AI agent does not need to implement x402 or MPP, hold wallet keys or construct a payment transaction itself. The wallet remains under the customer's ownership while Mitu handles the payment using the capabilities the customer has been given.

> **Current pay schema**
>
> See the current `pay` tool schema for the exact supported arguments. Do not build against the older endpoint-based form that accepted an API path, HTTP method and request body.

When the customer has several wallets, the payment needs to identify which wallet the customer intends to use. Mitu does not silently switch to another wallet when a wallet name is missing or unrecognised because doing so could spend money from a balance the customer did not choose.

See [Build agents that can pay](/guides/use-cases/agent-purchasing) for the end-to-end purchasing flow and [Agent payments](/platform/payments/agent-payments) for the underlying payment lifecycle.

## Wallet selection

Wallet selection becomes important when a customer has more than one balance. With a single wallet, the agent can use that wallet without asking the customer to distinguish between several options. With multiple wallets, any operation that moves money should preserve the customer's choice rather than guessing which wallet should fund the payment.

An unknown wallet name should not fall back to another wallet. The same principle applies when the customer has several wallets and the payment does not identify one clearly enough to determine their intent. Read-only operations such as checking balances can be more permissive because they do not move the customer's money.

See [Multiple wallets](/platform/agent-wallets/multiple-wallets) for the selection rules.

## What an AI agent cannot do

Wallet tools give an agent spending capabilities rather than ownership or administrative control. An agent cannot create a new Agent Wallet, withdraw the customer's funds, move money between wallets or change the spending controls configured for a wallet. Those decisions remain with your business or the customer, depending on the operation.

This boundary means a customer can allow an AI agent to complete permitted payments without giving the model unrestricted control over the underlying funds. Even when an agent is using the wallet, the money and the wallet continue to belong to the customer.

## Related

#### [Agent Wallets](/platform/agent-wallets/overview)

Understand wallet ownership and issuance.

#### [Funding](/platform/agent-wallets/funding)

Add funds to an Agent Wallet.

#### [Multiple wallets](/platform/agent-wallets/multiple-wallets)

Understand wallet selection when a customer has several balances.

#### [Build agents that can pay](/guides/use-cases/agent-purchasing)

Build an AI agent that completes payments using a customer's Agent Wallet.