VGA — NATIVE AGENT SETUP
The app runs on your own computer. This download contains no wallet or operator state.

START
Run Start-VGA.ps1 in the downloaded application folder, then open:
http://127.0.0.1:4391/explorer.html#agent-operations
Create a new encrypted vault in Agent wallets, or restore your own encrypted backup before starting. Unlock your vault to manage its agent wallets.
New native mainnet wallets are distinct keys; adding one never moves money.
Download an updated encrypted backup after creating native wallets.
Open Check technical setup in Agent operations for actual configuration status. Check connections performs public/read-only network and configured wallet-service checks, without funding, signing or a paid AI request.
Check-VGA.ps1 prints configuration only; Check-VGA.ps1 -CheckConnections performs the same connection checks. A working RPC does not prove an owned wallet is funded or approved.

NEAR MAINNET / GREEN APU
Choose a real agent, then Create mainnet NEAR wallet and its creation consent.
Inspect its mainnet account. The displayed 64-character implicit account is public.
Fund it yourself on NEAR MAINNET, or review the separately approved SOL bridge draft to this exact owned address.
A NEAR testnet account cannot receive mainnet funding. Existing seasons and bounties remain testnet.
Propose one exact transfer or contract call. Review receiver, amount/deposit, method/arguments/gas, fee, daily cap, finite runs and expiry.
Approve the permission, then independently review and confirm a manual run. A cadence authorizes finite repetition only while the local vault is unlocked.
Refresh reconciles the same hash and exact FINAL receipts. Pending/unknown transactions are never automatically resent.
While unlocked, the scheduler also reconciles pending hashes automatically, including after STOP or the last run. Reconciliation alone never broadcasts another transaction.
NEAR caps bound attached NEAR plus fee reserve. An exact contract method can affect other tokens or application state; those economic effects are not measured by the native NEAR cap.

STARKNET MAINNET / BLUE APU
Open Connect mainnet RPC. Enter a functioning external HTTPS Starknet RPC URL in the masked field.
The URL is held in server memory only, including any provider key in its path. It must be re-entered after a restart unless supplied through STARKNET_RPC_URL outside the app.
The app verifies SN_MAIN, synchronization, RPC compatibility and the fixed OpenZeppelin account class/ABI before connecting. A failed check leaves the old provider intact.
Create the agent's independent encrypted Stark key and computed account address.
Inspect the account. Do not fund an address until inspection confirms the declared account class is compatible and deploymentAvailable is true.
Fund its exact address with native STRK, then review the fee and independently confirm account deployment. A computed address alone is not an operating account.
After deployed-account inspection, prepare an exact STRK transfer or one exact contract call.
Contract-call fee caps bound network fees; they do not measure the economic effects of arbitrary calldata. Those effects require separate exact-call consent.
Approve finite permission and then confirm a run. Successful receipts require the exact transaction and acceptance on L1; L2-only acceptance stays pending.

ZCASH / YELLOW APU
Native ZEC setup needs a local Zallet wallet and its synchronized Zebra backend. On Windows, install or configure WSL if needed.
The application does not install operating-system features or generate a Zallet seed automatically.
1. In Administrator PowerShell, run Install-Linux-for-Zcash.ps1 yourself. Restart if Microsoft requests it.
2. Open Ubuntu and create your own Linux username/password.
3. Follow the official Zallet installation and wallet-setup guides below. Use a supported Linux release; install the launcher and matching backend together. Review the official release notes and choose a supported version.
4. Configure a synchronized mainnet zebrad built with its indexer feature. Zallet's Zebra backend must be on the same Linux host, with read-only access to Zebra state and its indexer gRPC endpoint.
5. Initialize Zallet's encrypted key storage interactively, generate/import your own mnemonic, back it up and confirm the backup. The app never asks for this mnemonic. Keep Zallet's key backup separate from VGA's encrypted vault backup.
6. Keep Zallet RPC on loopback, e.g. 127.0.0.1:28232. Keep Zebra JSON-RPC on loopback, e.g. 127.0.0.1:8232. Never expose wallet RPC on a public interface.
7. Start the actual services and wait for their synchronization. Confirm getwalletstatus reports a usable synced wallet.
8. In Agent operations, choose Connect local Zallet. Enter the two loopback URLs and either the wallet's cookie-file path or its RPC username/password. A Windows cookie path may be under \\wsl.localhost\Ubuntu\home\YOUR_LINUX_USERNAME\.zallet\.cookie. Use your actual path; do not copy a wallet cookie into the app folder or chat.
9. Check and consent to this local wallet access. Credentials stay in server memory. The adapter uses dedicated direct loopback transport, without forwarding wallet authentication to an external HTTP proxy.
10. Create a distinct account for the selected agent. The app checks its real UUID, derivation and shielded-only Unified Address. Inspect exact confirmed zatoshi balances.
11. A reviewed SOL bridge draft can fund this actual mainnet receiving address when the provider supports the native ZEC destination. It grants no automatic spending permission.

ZCASH SPENDING LIMIT
The Zallet integration supports connection, distinct native receiving accounts and balance inspection. Autonomous outbound ZEC signing is disabled.
The current official PCZT inspection schema exposes optional creator-claimed shielded value/address metadata and does not provide independently verifiable owned-change information for this signing guard. It would be misleading to label such an autonomous payment verified. Installing Zallet alone does not enable outbound native transfers in VGA.
You can still use the separately reviewed SOL-to-ZEC bridge and manage received ZEC in your own Zallet wallet. Native outbound integration needs a suitable verified transaction-inspection adapter before it can be enabled.

AI ENGINES
Connect and test your own xAI or Meta Model API credentials through AI engines. No connected status is fabricated. Assign the verified engine to the actual permission.
Fixed exact rules work without an AI provider. AI proposes or waits; the separate signer enforces the frozen action, network, fee reserve, caps, run count and expiry.
Restarting the server clears in-memory provider credentials/RPC settings and locks the vault. No installation or restart sends funds.

SOURCES
Microsoft WSL installation: https://learn.microsoft.com/windows/wsl/install
Zallet installation: https://zcash.github.io/zallet/guide/installation/index.html
Zallet platform support: https://zcash.github.io/zallet/guide/platform-support.html
Zallet wallet setup: https://zcash.github.io/zallet/guide/setup.html
Zallet RPC reference: https://zcash.github.io/zallet/rpc/index.html
Zallet releases: https://github.com/zcash/zallet/releases
NEAR RPC networks: https://docs.near.org/api/rpc/providers
Starknet account lifecycle: https://starknet-js.com/docs/guides/account/create_account/
Meta Responses: https://dev.meta.ai/docs/protocols/responses
xAI Responses: https://docs.x.ai/developers/rest-api-reference/inference/responses
