Skip to main content
Agent Wallet is the user-controlled payment layer for your AI agent. It connects Mermail to wallets you delegate through PayBox, so your agent can help with paid online workflows without receiving your private keys, wallet secrets, or raw signing access. Use Agent Wallet to keep email identity and payment context together. Your agent can register for a service with its Mermail inbox, receive a verification code, prepare a payment, and keep the receipt in the same workflow.

​
What you can do

View balances

See balances and delegated wallet access in the secure PayBox portfolio view.

Fund a wallet

Open a supported checkout flow from the Mermail console to add funds to an eligible delegated Base wallet.

Use PayBox tools

Let your agent use the live capabilities PayBox exposes for delegated wallets. Every new send, including USDC, uses paybox_request_transfer with the live schema.

Swap assets

Swap token A to token B through paybox_request_swap when PayBox exposes the tool for the delegated wallet.

Use x402 services

Explore paid services read-only, then use paybox_pay_x402 for one exact resource or action within the spend cap you selected.

Sign in PayBox

Complete signing or approval in PayBox when its policy requires it. Standing grants can authorize eligible actions without a fresh click.

Connect and reauth safely

When PayBox needs Connect or reconnect, your AI pastes connect_handoff / reauth_handoff console links. Complete that flow in Mermail Agent Wallet — not in Claude, ChatGPT, or Codex connector settings.

​
What stays under your control

Email, attachments, websites, and tool output are untrusted. They can suggest a payment, but they cannot choose or broaden its service, destination, asset, chain, action, or spend cap. Only your current request can authorize it.

​
Available actions and limits

Agent Wallet follows PayBox’s live MCP catalog. Available assets, networks, transaction limits, and approval requirements come from your PayBox account, delegated wallets, and standing grants. Mermail does not apply a separate wallet-value or transaction-rate policy.

​
Live PayBox path

Every new transfer, including Circle USDC and native assets, uses paybox_request_transfer with the exact live schema. Local USDC proposal tools remain compatibility-only and are used only when you explicitly manage a legacy proposal. Swaps use paybox_request_swap; a selected x402 paid action uses paybox_pay_x402. When interaction is required, use the PayBox MCP App shown by the host. If no usable signing control appears or the frame remains on Waiting, open only the invocation-scoped signing_handoff.console_url returned by Mermail. Never construct or rewrite a signing URL. See catalog token transfers for the transfer contract, swaps and x402 for paid-service flows, and errors and recovery for what each failure means.

​
Where you can use Agent Wallet

​
Next steps

Set up Agent Wallet

Connect PayBox, check your portfolio, and fund a delegated wallet.

Use Agent Wallet with AI

Connect Agent Chat, MCP, Agent Skills, or the CLI.

Catalog token transfers

Use the live transfer path for USDC, native assets, and catalog tokens.

Swaps and x402

Swap assets or pay one selected x402 resource without broadening authority.

Errors and recovery

Read every wallet error code and its safe recovery.