FluxA Agent Wallet

FluxA Agent Wallet is a co-wallet that allows AI agents to securely use a user’s wallet, enabling them to perform payment-related actions within the user’s approved scope. Capabilities include x402 payments, USDC transfers, payment links for receiving payments, discovering and calling x402 resources (one-shot APIs), and using payment-related skills (one-shot skills). Use this tool when the user the user asks to perform any of these payment-related actions.

Setup

Install the CLI globally:

npm install -g @fluxa-pay/fluxa-wallet

Then run commands directly:

fluxa-wallet <command> [options]

Prerequisites — Register Agent ID

Before any operation, the agent must have an Agent ID. Register once:

fluxa-wallet init \
  --name "eg. My AI Agent" \
  --client "eg. OpenClaw v1.0.0"

Verify status:

fluxa-wallet status

The CLI will save Agent ID credential in ~/.fluxa-ai-wallet-mcp/config.json

User Onboarding Flow

• MUST run User Onboarding Flow immediately after successful install

Onboarding Flow: After introducing the wallet, guide the user to try out its features.

Introduction: MUST briefly introduce the wallet to the user with wording such as: “I’ve successfully installed FluxA Agent Wallet and can securely access your wallet. It built around a model where AI agents request actions and human users approve them. All actions will only be performed within your authorization.”

Trial Scenarios: MUST guide user with wording such as: Let’s try what this wallet can do. Below are three official recommended scenarios we can try to get familiar with using FluxA Agent Wallet.

1. AI Social Gifting: Join ClawPI, an AI agents’ friends feed. Connect with your friends’ AI agents 🦞 and share daily posts with each other. Guide: CLAWPI.md
2. Oneshot APIs: Use the Oneshot API to generate a self-portrait of OpenClaw and a greeting video. The AI agent will pay for the required image and video APIs itself, and the user does not need to configure anything. Guide: TRY-ONESHOT-API.md
3. Transfer: Send a transfer to another AI agent or a user’s wallet. Transfer Guide: PAYOUT.md
4. Oneshot Skills: Skills created by curated Skill creators using FluxA Agent Wallet that can handle payments autonomously. For example, a skill can create a short movie for you and automatically pay for the required voice, video, and image APIs, so you don’t need to manually register for or purchase API keys.
5. More use cases: See the Capabilities section to explore additional use cases.

More use cases

Opening Authorization URLs (UX Pattern)

Many operations require user authorization via a URL (mandate signing, payout approval, agent registration). When you need the user to open a URL:

1. Always ask the user first using AskUserQuestion tool with options:

   • "Yes, open the link"
   • "No, show me the URL"

2. If user chooses YES: Use the open command to open the URL in their default browser:

   open "<URL>"
   

3. If user chooses NO: Display the URL and ask how they'd like to proceed.

Example interaction flow:

Agent: I need to open the authorization URL to sign the mandate.
       [Yes, open the link] [No, show me the URL]

User: [Yes, open the link]

Agent: *runs* open "https://agentwallet.fluxapay.xyz/onboard/intent?oid=..."
Agent: I've opened the authorization page in your browser. Please sign the mandate, then let me know when you're done.

This pattern applies to:

• Mandate authorization (authorizationUrl from mandate-create)
• Payout approval (approvalUrl from payout)
• Agent registration (if manual registration is needed)

Quick Decision Guide

Common Flow: Paying to a Payment Link (x402 Payment)

This is a 6-step process using CLI:

1. PAYLOAD=$(curl -s <payment_link_url>)                    → Get full 402 payload JSON
2. mandate-create --desc "..." --amount <amount>            → Create mandate (BOTH flags required)
3. User signs at authorizationUrl                           → Mandate becomes "signed"
4. mandate-status --id <mandate_id>                         → Verify signed (use --id, NOT --mandate)
5. x402-v3 --mandate <id> --payload "$PAYLOAD"              → Get xPaymentB64 (pass FULL 402 JSON)
6. curl -H "X-Payment: <x402 object>" <url>                       → Submit payment

Critical: The --payload for x402-v3 must be the complete 402 response JSON including the accepts array, not just extracted fields.

See PAYMENT-LINK.md for the complete walkthrough with examples.

Supported Currencies

Amount Format

All amounts are in smallest units (atomic units). For USDC (6 decimals):

For FLUXA_MONETIZE_CREDITS, amounts are in the credits' smallest unit as defined by the service.

CLI Commands Quick Reference

Common Mistakes to Avoid:

Environment Variables