Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.anyway.sh/llms.txt

Use this file to discover all available pages before exploring further.

Give your AI agent a dedicated USDC wallet on Base. The agent spends autonomously through the SuperAPI, while you set the limits. Up to 5 per organization.

​
Getting Started

​
Step 1: Create Agent Wallet

  1. Go to Wallets → click + Create Agent Wallet
  2. Enter a name and spending limit (max per transaction, default $5)
Create Agent Wallet dialog with name and spending limit fields
  1. Click Create — the wizard creates the wallet, generates the signing keypair, delegates access, and sets the spending policy in one step. By default, the agent gets a $5 max per transaction cap and direct sends are blocked (the agent can only pay through x402, not transfer USDC freely)
  2. Save the Agent Token — it’s shown once and cannot be retrieved later. You can also copy the CLI Bundle to import the agent on another machine
You can update the spending limit anytime via the Edit (pencil icon) on the agent wallet card.

​
Step 2: Fund the Wallet

On the agent wallet card, click ↓ Fund to transfer USDC from your main wallet to the agent wallet.Fund Agent Wallet dialog showing From, To, and Amount fields

​
Step 3: Buy Something

Your agent can now buy APIs on the SuperAPI. The spending limit you set is enforced automatically — if the agent tries to exceed it, the payment is rejected. See the SuperAPI Quick Start for a complete code example.

​
Step 4: Monitor & Manage

From the Agent Wallets page:Agent wallet management page with Fund, Withdraw, and Reset buttons
  • ↓ Fund / ↑ Withdraw — transfer USDC between main wallet and agent wallet
  • Edit (pencil icon) — update the spending limit
  • Reset Agent Access — rotate the signing key (wallet address + balance preserved)

​
How It Works

Agent → sign with P-256 key → Privy MPC signs USDC transfer → x402 payment settles on Base
When the agent makes a payment:
  1. The agent builds an EIP-712 typed data payload (USDC TransferWithAuthorization)
  2. It signs a request to Anyway’s backend using its P-256 key — this proves identity
  3. Anyway forwards the request to Privy, which checks the spending policy
  4. If the policy allows it, Privy’s MPC wallet produces a secp256k1 signature — this authorizes the USDC transfer
  5. The agent sends this signature to the SuperAPI via the x402 protocol, and the payment settles on Base
The agent never holds the wallet’s private key. It only holds a P-256 signing key that authorizes Privy to sign on its behalf, within the limits you set.

​
Zero Custody

KeyWhere it livesWho can access it
Wallet key (secp256k1)Privy embedded wallet — created client-side in your browserPrivy MPC (no single party holds the full key)
Agent signing key (P-256)Agent’s local machine or runtimeOnly the agent
Anyway never sees or stores either key.

​
Spending Policies

Policies are enforced by Privy at the MPC signing layer — not by Anyway’s backend. This means even if the backend is compromised, the agent cannot spend beyond its limits. Default rules on every new agent wallet:
  • Max per transaction ($5 by default) — caps each x402 payment
  • Block direct sends — the agent can only pay through x402, not transfer USDC freely on-chain