axonpayDocs

Control & safety/ UTILITY 9Live

Agent Wallet

Every agent spends from its own Solana keypair, never yours. You create it in the browser, fund it with what it is allowed to lose, and can empty it at any time.

On this page+

Create one

  1. 1
    Open the dApp, sign in with your main wallet (Phantom, Solflare or Backpack) and go to Build & control → Agent wallets.
  2. 2
    Click New agent wallet, name the agent and choose a password. The keypair is generated in that browser tab.
  3. 3
    The secret key is encrypted right there (PBKDF2-SHA256 with 600,000 iterations, then AES-256-GCM with the address bound in) and saved in this browser’s local storage under your signed-in address. Axonpay never receives the key or the password and keeps no copy.
  4. 4
    Download the encrypted backup it offers. Without it, clearing this browser’s storage loses the wallet, and another browser or device won’t see it until you import the backup there.
  5. 5
    Fund it from your main wallet with USDC. The first USDC transfer also creates the agent’s USDC account, which costs you about 0.002 SOL of rent once and comes back when you sweep.

Run an agent with it

Reveal the secret key (the password is required): you get base58 of the 64-byte secret. Give it to the process that runs the agent. Treat it like the cash in a till: whoever holds the key can spend whatever is in the wallet.

.env
# base58 of the 64-byte secret, from Reveal on the Agent wallets page
AGENT_SECRET_KEY=<base58 secret>
SOLANA_RPC_URL=<your RPC URL>

The agent needs no SOL to pay x402 calls, because the seller’s facilitator pays the network fee. The key plugs straight into createKeyPairSignerFromBytes from @solana/kit; see Quickstart: agents.

Import an existing key

Import on the same page accepts an Axonpay backup file (with its password), or a raw secret key: base58, as Phantom exports it, or a JSON array of 64 numbers, as solana-keygen writes it. Either way the key is re-encrypted under a password you choose before it is stored.

Why a separate wallet

  • Small blast radius. A compromised or prompt-injected agent can lose its own balance and nothing more.
  • Clean books. Every outgoing signature from this address is that agent’s spend, nobody else’s.
  • Easy to revoke. No approvals to hunt down. Sweep the balance back and abandon the key.
  • One rulebook per agent. Each wallet gets its own mandate.

What it is not

An agent wallet is a plain keypair, not a smart wallet or a program account. Its rules are enforced by the client library, so a copy of the key running other code would ignore them. That is why the balance itself is the hard limit: fund agents for a day or a week, not for a year. On-chain mandates (planned) would move the rules into a program that even a leaked key can’t bypass.