Step 2 of 6

Start with the narrowest template that supports the agent's first task. Review the generated controls before completing setup.

Choose a starting template

Use Spot swapper for a narrowly scoped spot-swapping agent. Use Perp trader for the perpetual-trading context offered in the preview.

A template is only a starting point. Review the generated venue, network, asset, recipient, contract, function, trade-side, slippage, leverage, and sanctions controls that apply to the selected execution context. The complete set is documented in Policy checks.

For a Spot swapper, recipient configuration has three distinct meanings. Omit the recipient allowlist to disable the external-recipient check. Keep it empty to permit only the agent's own registered wallets. Add reviewed addresses to permit those addresses as well as the agent's own wallets.

For a Perp trader, review the per-transaction cap, rolling 24-hour outflow cap, leverage update cap, portfolio leverage cap, and optional per-protocol exposure cap. These limits depend on price and position state; unavailable state fails closed.

Set deliberately narrow limits

1. Permit only the venue and network required for the first test.
2. Limit the asset or market universe to the immediate task.
3. Add only reviewed recipients, contracts, and functions.
4. Set trade-side, slippage, execution-price, and leverage limits where shown.
5. Keep sanctions controls enabled.
6. Review each value before continuing.

Do not relax a control simply to make an action pass. Start narrow, observe real verdicts, and widen one reviewed capability at a time.

Complete the final review

Compare the final review with the registration and policy you intended. In particular, check the wallet, network, template, assets, and numeric limits.

When the dashboard reveals the agent API key:

1. Copy it directly into the approved secret manager.
2. Name the secret for this agent and environment.
3. Restrict which people and services can read it.
4. Complete the displayed connection instructions.
5. Install or link the bundled Nava agent skill when this agent will operate through a skill-aware host.
6. Leave the key out of tickets, chat, source files, logs, screenshots, and shell history.

The key is shown once. If it may have been exposed or was not stored correctly, use the supported rotation workflow instead of trying to recover it.

Confirm setup

The agent should now appear on the dashboard with the intended wallet and an active policy version. Send only a controlled test action before widening its scope.