Takeover Wallet

Binding is the moment when an existing wallet becomes attached to your account. Before binding, the wallet may live on the agent or sandbox side. After binding, the dashboard can treat it as your wallet and show it alongside the rest of your account.

This does not create a new wallet. It links the wallet you already have to the user account that will manage it. That is why bind is important: it turns a wallet from an isolated agent asset into something you can inspect, govern, and operate from the product UI.

If you want the exact step-by-step flow, read the install guide or the quickstart. This page is focused on the meaning of binding and the capabilities it unlocks afterward.

Binding and risk control belong together. A wallet that is attached to your account should not be able to do everything with no limits. The risk policy is where you tell the wallet what is allowed, what needs extra confirmation, and what should never happen.

After bind, you can set transfer limits, approval thresholds, allowlists, denylists, and other guardrails. That lets you use the wallet for real work without making it unsafe by default.

In practice, this means the wallet can stay useful for normal operations while still forcing a pause on dangerous actions such as large transfers, unknown recipients, or risky token interactions.