Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.operator.io/llms.txt

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

Create agentic wallets with policy guardrails for autonomous onchain transactions

Capabilities

Once connected, your agent can perform these actions with crypto wallets.
  • Create server wallets on 10+ chains
  • Set spending limits and policy rules
  • Execute autonomous transactions
  • Multi-chain support (10+ networks)
  • Agent-to-agent payments
  • DeFi operations with contract allowlists
  • Policy-based transaction guardrails
  • Sign messages and typed data

Setup Guide

Follow these steps to connect Privy to your instances.

1. Create a Privy account and app

Go to dashboard.privy.io and create an account. Then create a new app for your agent wallets.

2. Get your API credentials

Navigate to Configuration → App settings → Basics. You’ll find your App ID and App Secret.

3. Store credentials in Environment

Go to Environment and create two new variables:
  • Name: PRIVY_APP_ID Value: Your Privy App ID
  • Name: PRIVY_APP_SECRET Value: Your Privy App Secret (keep this secure!)

4. Grant access to instances

Choose how instances should access these credentials:
  • Option A: Global Access (All instances) — Toggle “Make globally accessible” when creating the secrets.
  • Option B: Instance-Specific (Selective access) — In Environment, open the secret and grant the specific instance access.

Supported Chains

Create wallets on any of these blockchains.
ChainCAIP-2 Identifier
Ethereumeip155:1
Baseeip155:8453
Base Sepoliaeip155:84532
Polygoneip155:137
Arbitrumeip155:42161
Optimismeip155:10
Solanasolana:mainnet
Extended support: Cosmos, Stellar, Sui, Aptos, Tron, Bitcoin (SegWit), NEAR, TON, StarkNet

Security & Policies

All wallets should have policies attached to control agent behavior.
⚠️ Mandatory Security Rule Never create a wallet without a policy. Policies define spending limits, chain restrictions, and contract allowlists to prevent abuse.

Example Policy

Conservative policy with 0.01 ETH limit on Base mainnet:
{
  "name": "Conservative agent policy",
  "chain_type": "ethereum",
  "rules": [
    {
      "name": "Max 0.01 ETH per transaction",
      "method": "eth_sendTransaction",
      "conditions": [{
        "field": "value",
        "operator": "lte",
        "value": "10000000000000000"
      }],
      "action": "ALLOW"
    },
    {
      "name": "Base mainnet only",
      "method": "eth_sendTransaction",
      "conditions": [{
        "field": "chain_id",
        "operator": "eq",
        "value": "8453"
      }],
      "action": "ALLOW"
    }
  ]
}

Usage Example

Ask your agent:
“Create an Ethereum wallet on Base with a policy that limits transactions to 0.05 ETH max”
The agent will automatically create a policy with your constraints, create a wallet with that policy attached, and return the wallet address.