For a brokerage account, import a readable statement or CSV; Vivi does not provide a live broker connection. For supported exchanges, use a key with the required read-only permissions. For supported wallets, connect or watch a public address.

A read-only exchange key is still sensitive. It can reveal account activity, even though it cannot place an order. A public wallet address can also connect financial activity to your identity.

1. Input

   Choose a statement, a supported exchange’s read-only key or a wallet address. Never provide an exchange password, seed phrase or private key.

2. Permission check

   Vivi checks supported exchange key permissions and rejects trading or withdrawal access, as well as permissions it cannot verify. Keep keys in the dedicated connection flow, not in a chat message or upload.

3. Output

   Review the holdings and the connection’s coverage. Unsupported assets, missing prices or incomplete responses must be considered separately from the available balance.

Connection choices, not a promise that every provider, chain or asset is supported.

Example requestI want to understand these holdings, not move them. Which connection method and permissions do I need?

Supported providers and chains have different coverage and permission models. A successful connection does not mean every asset, transaction or price is available.

Vivi keeps exchange credentials encrypted and outside the AI’s working files. This limits exposure; it is not a guarantee against every security risk.

Review permissions at the provider and revoke a key there when you no longer need it. Disconnecting in Vivi and revoking at the provider are separate actions. Vivi cannot hold, send or trade your money.