AgentWallex Payment Skill

What It Does

The AgentWallex Payment skill gives AI agents core capabilities for managing agents and crypto payments:

• Zero-config setup — Set up AgentWallex through conversation. No config files or environment variables needed.
• Create and manage agents — Create, update, suspend, and delete AI agents with dedicated wallets.
• Multi-chain support — Operate across Ethereum, BSC, and Tron networks.
• Check token balances — Query available, locked, and pending balances for any agent wallet on supported chains.
• Send outbound transfers — Create and submit on-chain USDC/USDT transfers to any recipient address.
• Query transaction status — Track payment lifecycle from pending through confirmed or failed, with full tx hash details.

Supported Chains & Tokens

Mainnet

Sandbox (Testnet)

Start with sandbox for development and testing. Sandbox transactions use testnet tokens and don't cost real money.

Requirements

No API key or environment variable is needed upfront — credentials are configured through conversation and stored locally.

Setup

Install via ClawHub:

clawhub install agentwallex-openclaw

Then tell your AI agent:

"Set up AgentWallex"

The agent will use the agentwallex_setup tool and guide you through:

1. Opening the AgentWallex Dashboard (sandbox) or Production Dashboard
2. Signing in with Google
3. Creating an API key (starts with awx_)
4. Copying your Agent ID
5. Pasting the credentials back — they're validated and saved automatically

Credentials are stored locally at ~/.openclaw/agentwallex/config.json with owner-only permissions (0600). No environment variables needed.

Reconfiguring

To change credentials or switch agents, just say:

"Reconfigure AgentWallex with my new API key awx_xxx and agent ID agent-123"

The agent will validate the new credentials and update the local config.

Upgrade

Update to the latest version:

openclaw plugins update @agentwallex/agentwallex-openclaw

Or update all plugins at once:

openclaw plugins update --all

Uninstall

openclaw plugins uninstall @agentwallex/agentwallex-openclaw

To keep plugin files on disk:

openclaw plugins uninstall @agentwallex/agentwallex-openclaw --keep-files

To also remove locally stored credentials:

rm -rf ~/.openclaw/agentwallex

Available Tools

API Reference

Environments

Start with sandbox for development and testing. Switch to production when ready to go live.

# Set the base URL (default: sandbox)
export AGENTWALLEX_BASE_URL="https://api-sandbox.agentwallex.com/api/v1"

All requests require the API key header:

X-API-Key: <your-api-key>

Response Format

Success (single object): Returns the object directly, no envelope.

{
  "agent_id": "agent-a1b2c3",
  "agent_name": "payment-bot",
  "chain": "ethereum",
  "status": "active"
}

Success (paginated list):

{
  "data": [ ... ],
  "total": 42,
  "has_more": true
}

Error:

{
  "code": "not_found",
  "type": "not_found_error",
  "message": "Agent not found"
}

Error types: validation_error (400), authentication_error (401), authorization_error (403), not_found_error (404), conflict_error (409), rate_limit_error (429), internal_error (500), service_unavailable (503).

Pagination Parameters

All list endpoints support:

Create Agent

Creates a new AI agent with its own wallet on the specified chain. Returns 201 Created.

curl -s -X POST \
  "$AGENTWALLEX_BASE_URL/agents" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_name": "payment-bot",
    "chain": "ethereum",
    "agent_description": "Handles outbound payments"
  }' | jq

Request body:

Response — An Agent object:

List Agents

Lists all agents accessible to the current API key, with optional filtering.

curl -s -X GET \
  "$AGENTWALLEX_BASE_URL/agents?status=active&page_num=1&page_size=20" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" | jq

Query parameters:

Response — A paginated list:

{
  "data": [
    {
      "agent_id": "agent-a1b2c3",
      "agent_name": "payment-bot",
      "chain": "ethereum",
      "status": "active",
      "wallet_address": "0x...",
      "created_at": "2025-03-01T12:00:00Z"
    }
  ],
  "total": 1,
  "has_more": false
}

Check Balance

Returns balances for a specific agent (one entry per chain/token).

curl -s -X GET \
  "$AGENTWALLEX_BASE_URL/agents/AGENT_ID/balance" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" | jq

Response — An array of balance objects (one per chain/token):

Get Deposit Address

Returns a deposit address for funding the agent wallet. EVM chains (Ethereum, BSC) share the same address.

curl -s -X POST \
  "$AGENTWALLEX_BASE_URL/agents/AGENT_ID/deposit" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "chain": "ethereum"
  }' | jq

Request body:

Response:

{
  "agent_id": "AGENT_ID",
  "chain": "ethereum",
  "address": "0x..."
}

Transfer

Initiates a transfer from an agent's wallet.

curl -s -X POST \
  "$AGENTWALLEX_BASE_URL/agents/AGENT_ID/transfer" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "10.00",
    "to_address": "0xRecipientAddress",
    "chain": "ethereum",
    "token": "USDC"
  }' | jq

Request body:

Response:

Get Transaction Status

Retrieves the current status and details of a transaction.

curl -s -X GET \
  "$AGENTWALLEX_BASE_URL/transactions/TRANSACTION_ID" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" | jq

Response:

List Transactions

Lists transactions with optional filtering. Transactions are read-only.

curl -s -X GET \
  "$AGENTWALLEX_BASE_URL/transactions?agent_id=AGENT_ID&status=completed&page_num=1" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" | jq

Query parameters:

Workflow Examples

Flow 1: Check Balance, Send Payment, Verify Transaction

Step 1 — Check the agent's available balance:

curl -s -X GET \
  "$AGENTWALLEX_BASE_URL/agents/AGENT_ID/balance" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" | jq '.[0].available'

Step 2 — Transfer funds (only if balance is sufficient):

TX=$(curl -s -X POST \
  "$AGENTWALLEX_BASE_URL/agents/AGENT_ID/transfer" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "10.00",
    "to_address": "0xRecipientAddress",
    "chain": "ethereum",
    "token": "USDC"
  }')

TX_ID=$(echo "$TX" | jq -r '.transaction_id')
echo "Transaction ID: $TX_ID"

Step 3 — Check the transaction:

curl -s -X GET \
  "$AGENTWALLEX_BASE_URL/transactions?agent_id=AGENT_ID&status=completed" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" | jq '.data[0]'

Flow 2: Create Agent, Fund Wallet, Send Payment

Step 1 — Create a new agent:

AGENT=$(curl -s -X POST \
  "$AGENTWALLEX_BASE_URL/agents" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "agent_name": "payment-bot",
    "chain": "ethereum",
    "agent_description": "Handles outbound payments"
  }')

AGENT_ID=$(echo "$AGENT" | jq -r '.agent_id')
echo "Agent ID: $AGENT_ID"

Step 2 — Get a deposit address for the new agent:

DEPOSIT=$(curl -s -X POST \
  "$AGENTWALLEX_BASE_URL/agents/$AGENT_ID/deposit" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"chain": "ethereum"}')

echo "Deposit to: $(echo "$DEPOSIT" | jq -r '.address')"

Step 3 — After funding, check balance and transfer:

# Check balance
curl -s -X GET \
  "$AGENTWALLEX_BASE_URL/agents/$AGENT_ID/balance" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" | jq '.[0].available'

# Transfer USDC
curl -s -X POST \
  "$AGENTWALLEX_BASE_URL/agents/$AGENT_ID/transfer" \
  -H "X-API-Key: $AGENTWALLEX_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "amount": "10.00",
    "to_address": "0xRecipientAddress",
    "chain": "ethereum",
    "token": "USDC"
  }' | jq

Guardrails & Safety

When using this skill, you MUST follow these rules:

• Never send to zero or null addresses. Always validate that to_address is a non-empty, properly formatted address before creating a transaction.
• Always check balance before sending. Query the agent's available balance and confirm it covers the intended amount plus potential fees.
• Verify transaction amounts are reasonable. Before submitting, confirm the amount matches the intended payment. Reject or flag amounts that appear unusually large.
• Confirm recipient address format. For EVM chains (Ethereum, BSC): address starts with 0x and is 42 characters. For Tron: address starts with T and is 34 characters.
• Verify token support on chain. Ethereum and BSC support USDC and USDT. Tron only supports USDT.

Error Handling

Troubleshooting