home / skills / openclaw / skills / pocket-money

This skill helps your agent manage funded wallets for Base USDC payments to x402 services with explicit human approval.

npx playbooks add skill openclaw/skills --skill pocket-money

Review the files below or copy the command above to add this skill to your agents.

Files (3)
SKILL.md
4.5 KB
---
name: pocket-money
description: Give your AI agent crypto wallets on Base. Create purpose-specific wallets, ask your human to fund each one, check balances, and manage budgets. No accounts, no KYC — just wallet addresses and USDC on Base.
metadata:
  openclaw:
    requires:
      bins:
        - node
        - npm
      config:
        - .auteng/wallets/
    install:
      - kind: node
        package: "@auteng/pocket-money"
        bins: []
    homepage: https://github.com/operator-auteng-ai/pocket-money
---

# Pocket Money — Fund Your Agent's Wallets

You have a tool that lets you create and manage crypto wallets (USDC on Base). Each wallet is a separate keypair with its own balance — create one per purpose or budget.

**Package**: [`@auteng/pocket-money`](https://www.npmjs.com/package/@auteng/pocket-money) — published by AutEng ([source on GitHub](https://github.com/operator-auteng-ai/pocket-money)).

## Setup (first time only)

Install the pocket-money library:

```bash
npm install @auteng/pocket-money
```

## Creating a Wallet

Create a named wallet for each purpose or budget:

```typescript
import { wallet } from '@auteng/pocket-money';

const w = await wallet.create({ name: "feb-2026" });
console.log(w.address); // 0xABC123...
```

If a wallet with that name already exists on disk, it loads it. Each wallet is stored at `.auteng/wallets/<name>.json`.

You can also create a quick default wallet:

```typescript
const w = await wallet.create();
```

### Network

```typescript
// Base mainnet (default)
const w = await wallet.create({ name: "prod" });

// Base Sepolia testnet
const w = await wallet.create({ name: "test", network: "base-sepolia" });
```

## Requesting Funding

When you need money, ask your human to fund a specific wallet:

```
I need $12 in USDC for today's tasks.

Please send USDC on **Base** to this address:
`0xABC123...` (wallet: "feb-2026")

You can send from Coinbase, an exchange, or any wallet that supports Base.
```

Be specific about:
- **How much** you need and **why** (e.g., "$5 for API calls", "$20 for a batch processing job")
- **Which wallet** (by name) so both you and your human can track budgets
- The **network**: always Base (not Ethereum mainnet, not Arbitrum)
- The **token**: USDC (not ETH, not other tokens)

## Waiting for Funding

After asking, wait for the USDC to arrive:

```typescript
await w.waitForFunding(12_000000n);
// Polls Base every 10s until >= 12 USDC is available
```

With a timeout:

```typescript
await w.waitForFunding(12_000000n, { timeout: 120_000 });
// Throws after 2 minutes if balance < $12
```

Tell your human you're waiting — they may need a minute to complete the transfer.

## Human Approval Before Spending

**IMPORTANT**: Before making any payment, you MUST:

1. Tell your human exactly what you're about to spend and why
2. Show the estimated cost
3. **Wait for explicit human approval** before proceeding

Example:

```
I'd like to call an x402 API endpoint.

  Service: api.example.com/generate
  Cost:    ~$0.05 per request
  Wallet:  "feb-2026" ($0.98 remaining)

OK to proceed?
```

Never batch multiple paid operations without listing them first. If running a loop of paid calls, present the total estimated cost upfront and get approval for the batch.

## Managing Wallets

```typescript
// Retrieve an existing wallet by name
const w = wallet.get("feb-2026");

// List all wallets
const all = wallet.list();
for (const w of all) {
  const bal = await w.checkBalance();
  console.log(`${w.name}: ${w.address} — ${bal} USDC`);
}

// Check balance
const balance = await w.checkBalance();
// Returns USDC in minor units (6 decimals)
// e.g., 12_000000n = $12.00
```

If running low, ask your human for more funding before expensive operations.

## Security & Storage

**Private keys**: Wallet private keys are stored as unencrypted JSON at `.auteng/wallets/<name>.json` with restricted file permissions (0600). These keys can sign USDC payment authorizations. If the file is leaked or the machine is compromised, funds in that wallet can be stolen. Treat wallet files like passwords.

**Network access**: This skill makes outbound HTTPS requests to:
- **Base RPC** (`mainnet.base.org`) — to check USDC balances

**Mitigations**:
- **Always get human approval** before any operation that spends funds
- Only fund wallets with small amounts appropriate for the task — treat them as petty cash, not savings
- Create separate wallets for separate budgets so you and your human can track spending
- Your wallets only need **USDC on Base** — no ETH needed for gas

Overview

This skill gives your AI agent purpose-specific crypto wallets (USDC on Base) so it can pay x402-enabled services like sandboxed compute. Create separate wallets per task or budget, ask a human to fund each address, then spend only after explicit human approval via the x402 protocol. No accounts or KYC required — just wallet addresses and USDC on Base.

How this skill works

The skill creates and loads named keypair wallets stored locally (.auteng/wallets/<name>.json) and exposes methods to check balance, wait for funding, and perform x402 payments. When a service returns 402 Payment Required the library signs a payment authorization and retries; payments are settled server-side via x402. Compute calls integrate directly: pass the wallet to compute.run or use wallet.fetch as a drop-in for any x402-enabled endpoint.

When to use it

  • Run short paid compute jobs or API calls that require micro-payments
  • Manage separate petty-cash budgets for different tasks or projects
  • Avoid KYC and centralized accounts while enabling on-demand payments
  • Control agent spending by requiring human approval before each payment
  • Archive or reproduce archived skill behavior that relies on small crypto payments

Best practices

  • Create one wallet per purpose or budget to simplify tracking
  • Always state exact amount, purpose, wallet name, and network when requesting funds (USDC on Base)
  • Wait for funds to arrive with waitForFunding before attempting paid operations
  • Show estimated cost and wait for explicit human approval before any spend or batch of spends
  • Keep wallet files secured and backed up; keys are local and irrecoverable if lost

Example use cases

  • Pay for a one-off Python run on sandboxed compute using a dedicated compute wallet
  • Create a testing wallet for API calls and fund it with small USDC amounts to control risk
  • Use separate wallets for research, production experiments, and demos so budgets don’t mix
  • Archive agent behavior that depended on x402 payments and reproduce it in a test environment
  • Automate request-for-funding messages that include address, amount, reason, and wallet name for easy human approvals

FAQ

Which token and network do I use?

Use USDC on the Base network only. Do not send ETH or other tokens to these wallets.

Do I need ETH for gas?

No. These wallets only need USDC on Base; payments are handled via x402 without separate gas payments.

How do I ensure the agent won’t spend without permission?

Always require the agent to present estimated cost and receive explicit human approval before processing any payment or batch of payments.