Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Manage crypto wallets and make x402 micropayments with USDC stablecoins on Polygon
Manage crypto wallets and make x402 micropayments with USDC stablecoins on Polygon
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Use llm-wallet commands to manage crypto wallets and make micropayments to paid APIs using USDC stablecoins on Polygon blockchain. Default Network: Polygon Testnet (polygon-amoy) - safe for testing Facilitator: https://x402-amoy.polygon.technology
# Create wallet llm-wallet create # Check balance llm-wallet balance # Set spending limits (recommended) llm-wallet set-limit --per-tx 0.10 --daily 5.00 # View transaction history llm-wallet history
llm-wallet create [--label <name>] Creates a new HD wallet with encryption. Returns wallet address. Example: llm-wallet create --label "agent-wallet"
llm-wallet import --private-key <key> [--label <name>] Import existing wallet from private key.
llm-wallet balance Shows USDC balance and native token balance on current network.
llm-wallet history View all transactions and payments made from this wallet.
llm-wallet set-limit --per-tx <amount> --daily <amount> Set per-transaction and daily spending caps in USDC. Example: llm-wallet set-limit --per-tx 0.10 --daily 5.00
llm-wallet get-limits View current spending limits and daily usage.
llm-wallet pay <url> [--method GET|POST] [--body <json>] Make x402 micropayment to a paid API endpoint. β οΈ IMPORTANT: Always ask user for approval before making payments! Example: # Ask user: "I need to make a payment to https://api.example.com/weather. Cost: $0.001 USDC. Approve?" llm-wallet pay "https://api.example.com/weather?location=London" Workflow: Check if payment is needed: llm-wallet check-payment <url> Show user: URL, estimated cost, current limits Wait for user approval Execute: llm-wallet pay <url> Confirm completion and show transaction ID
llm-wallet check-payment <url> Checks if wallet can afford payment without executing it.
llm-wallet register-api <url> --name <tool_name> Register a paid API endpoint as a reusable tool. Example: llm-wallet register-api "https://api.example.com/weather" --name weather_api
llm-wallet list-apis Show all registered API tools.
llm-wallet call-api <tool_name> [--params <json>] Execute a registered API tool. Requires approval if payment needed. Example: # Ask user for approval first if cost > 0 llm-wallet call-api weather_api --params '{"location": "London"}'
llm-wallet unregister-api <tool_name> Remove a registered API tool.
llm-wallet verify-payment --header <x-payment-header> --requirements <json> Verify incoming payment from a buyer (seller-side).
llm-wallet create-requirements --price <amount> --pay-to <address> --url <resource-url> Generate payment requirements for a protected resource.
Network Default: Always uses polygon-amoy (testnet) unless configured otherwise Approval Required: Always ask user before making payments Spending Limits: Check limits before payment attempts Transaction Logging: All payments are logged with timestamps Encryption: Wallets are encrypted with AES-256-GCM
WALLET_ENCRYPTION_KEY - Wallet encryption key (32+ chars, auto-generated if missing) WALLET_NETWORK - Network selection (default: polygon-amoy | polygon) FACILITATOR_URL - Custom facilitator URL (auto-configured) WALLET_MAX_TX_AMOUNT - Per-transaction limit override WALLET_DAILY_LIMIT - Daily limit override
Polygon Testnet (Amoy): Chain ID 80002, Facilitator: https://x402-amoy.polygon.technology Polygon Mainnet: Chain ID 137, Facilitator: https://x402.polygon.technology
# 1. Create wallet llm-wallet create --label "my-agent" # 2. Set spending limits llm-wallet set-limit --per-tx 0.10 --daily 5.00 # 3. Check balance (will be 0 initially) llm-wallet balance # 4. Fund wallet with testnet USDC # User needs to: visit https://faucet.polygon.technology/
# 1. Pre-check payment llm-wallet check-payment "https://api.example.com/weather?location=London" # 2. Show user: URL, cost estimate, current limits # 3. Ask user: "Approve payment of $0.001 USDC to https://api.example.com/weather?" # 4. If approved, execute payment llm-wallet pay "https://api.example.com/weather?location=London" # 5. Confirm and show transaction ID llm-wallet history
# 1. Register the API llm-wallet register-api "https://api.example.com/translate" --name translate_api # 2. List available APIs llm-wallet list-apis # 3. Call the API (with approval) llm-wallet call-api translate_api --params '{"text": "hello", "to": "es"}' # 4. View payment in history llm-wallet history
Insufficient Balance: Show error and guide user to faucet (testnet) or funding instructions (mainnet) Payment Rejected: Transaction reverted, check error message for details Limit Exceeded: Show current limits and daily usage, suggest increasing limits Network Timeout: Retry with exponential backoff (max 3 attempts)
See references/ folder for: x402-protocol.md - x402 payment protocol overview wallet-setup.md - Detailed wallet setup guide examples.md - More usage examples
All amounts are in USDC (6 decimals) Default network is testnet for safety Testnet USDC has no real value Always verify network before mainnet usage Keep encryption key secure (never share or commit)
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.