Agent Wallet

Give automation limits, not full wallet control

Use this page when you want an AI agent to trade with limits. It creates a separate wallet for the agent, keeps the settings key with the owner, and lets you decide what the agent can do before it can spend anything.

Keys shown once: generation returns the private key, execution key, and settings key once. This page keeps the latest bundle only in the current browser tab so you can finish setup without retyping everything.
Keep the settings key to yourself: do not give it to the AI agent. The settings key is for the owner: check balances, review limits, and change permissions. The execution key is the one that can call spend routes, and it still works only within the limits you set here.

Why use an agent wallet instead of your regular wallet

Do not hand your main wallet to an AI

A regular wallet has no built-in limits for an AI agent. If you give the agent your main wallet secret, it can keep spending from that wallet and the owner has no separate management key to stop or limit it.

One key to spend, one key to manage

The execution key is the key the agent may use on allowed routes. The settings key stays with the user so they can check balances, review limits, change permissions, and keep the final say.

Start locked down

New agent wallets start with transfer disabled. That means an agent does not automatically get the ability to send SOL to arbitrary destinations until the user explicitly enables that capability.

How to use the two keys

Execution key

Give this key only to the automation layer that actually needs to call execution routes. Even then, it should operate under the policy limits you set on this page.

Settings key

Keep this key with the user or operator. It is meant for control, review, and policy updates. It should not be pasted into agent prompts, bots, chat tools, or swap and transfer builders.

Private key

This is the recovery path for the owner. Save it securely and do not use it as the routine way to power an AI workflow. The goal of the agent wallet model is to avoid giving full wallet control to the automation loop.

Current Rules

What the backend allows

Loading current agent wallet rules.

  • Waiting for live capabilities.
Headers

Auth model

X-Agent-Execution-Keyexecution only
X-Settings-Keyprofile and policy only
X-Idempotency-Keyrequired for agent execution
Setup

Recommended order

  1. Generate the wallet bundle and save all returned keys.
  2. Inspect profile and balances using the settings key.
  3. Apply policy limits before moving to transfer or swap.
Generate

Create agent wallet bundle

Click Generate agent wallet to create a new agent key bundle.
—
—
—
—
Bundle details: this generator works like the regular wallet page, but it returns two separate agent keys: one for spending routes and one for viewing and changing settings.
Request Preview

Generate request snippets

Loading snippet...
Request preview uses the live v1 control-plane route.
Response

Generation result

Status: No bundle generated yet.
{}
Inspect

Profile, balances, stats, and history

Request Preview

Inspect request snippets

Loading snippet...
Snippet follows the selected inspect route and current settings key field.
Response

Inspect result

Status: No inspect request sent yet.
{}
Settings

Agent policy control panel

Status: Paste a settings key and click Load settings.
Reference

What this settings panel controls

Loading the live contract for this settings panel.

Headers
Waiting for backend runtime.
Editable Here
Waiting for backend runtime.
Read Only
Waiting for backend runtime.
Live State

Current limits, remaining budget, and assignment dates

Load a settings key to see current limit values, remaining rolling budget, and the date each limit was assigned.

Per Transaction
No settings loaded yet.
Rolling Windows
No settings loaded yet.
Guardrails
No settings loaded yet.
Budget

Spend limits

Rolling limits Set one or more frame-based caps.

Each row defines one rolling cap. Frame, unit, amount, and delete stay on the same line for quick edits.

Capabilities

Allowed operations

Lightning tradeAllow the broader lightning execution surface.
Token createAllow token-builder create flows under agent policy.
Token claimAllow claim-only flows without enabling broader create access.
TransferAllow native SOL transfers on the dedicated route. Starts disabled on newly generated wallets.
SwapAllow dedicated v1 swap execution.
Transfer guardrails

Transfer-specific rules

Require transfer memoUse this when every outgoing transfer must include a human-readable note.
Restrict to allowlistOnly addresses in the list below will be accepted as transfer destinations.
Allowlist addresses One destination per row.

New wallets start with transfer off. If transfer capability is off, these controls lock automatically. If allowlist mode is off, the address list becomes inactive.

Request Preview

Settings request snippets

Loading snippet...
Snippet follows the current policy fields and selected language.
Response

Updated profile

Status: No settings update sent yet.
{}

Next surfaces

Operations Builder

Use the execution key for transfer and swap once the policy is configured the way you want.

Open operations

Lightning Builder

Reference the existing builder for the broader trade surface and shared routing engine behavior.

Open lightning

API Docs

Cross-check the public contract and error behavior for the production integration.

Open docs
Previous Page Operations Builder ←
Current Page AI Agents Wallet
Next Page Terms of Service →