🇺🇸English

FluxA Agent Wallet

Skill version: 0.3.4 | CLI version: @fluxa-pay/fluxa-wallet@0.3.2 — MUST use this exact CLI version. Install or update before use.

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, agent-to-agent transfers, payment links for receiving payments, AI social gifting, 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

Step 1 — Install the CLI

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

Then run commands directly:

fluxa-wallet <command> [options]

Step 2 — Init Wallet

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

First , check if the agent is already initialized:

fluxa-wallet status

If configured is true, the agent is already initialized — skip the init step. If init has already been run, running it again will be ignored.

If not initialized, register once:

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

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

Link to user’s wallet: After init, check if the agent is already linked:

fluxa-wallet check-wallet

• linked: true → proceed to Step 3
• linked: false → run fluxa-wallet link-wallet to get the authorization URL, then ask the user to open it using the “Opening Authorization URLs” UX pattern below.

Step 3 — User Onboarding Flow

MUST run User Onboarding Flow immediately after successful setup.

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 is 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 some 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)

Mandate Planning Policy

MUST follow when working with intent mandates:

1. Plan by task intent, not by API call. Assess the full task before creating a mandate — estimate total cost across all steps, create one mandate for the whole workflow.
2. Check for reusable mandates first. Before creating a new mandate, check both the current conversation context and ~/.fluxa-ai-wallet-mcp/mandates.json for existing signed, unexpired mandates that fit.

Full planning rules, task classification, and state file schema: MANDATE-PLANNING.md

Quick Decision Guide

Common Flow: Paying to a x402 url

This is a 6-step process using CLI:

1. curl -s <x402_url>                    → Get full 402 payload from JSON or response header
2. fluxa-wallet mandate-create --desc "..." --amount <amount>            → Create mandate (BOTH flags required)
3. User signs at authorizationUrl                           → Mandate becomes "signed"
4. fluxa-wallet mandate-status --id <mandate_id>                         → Verify signed (use --id, NOT --mandate)
5. fluxa-wallet x402 --mandate <id> --payload "<402 payload>"                 → Get signed x402 payment response
6. retry x402 url again with x402 payment response                   → Submit payment

Critical: The --payload for x402 must be the complete 402 response.

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

Developer Integration Guides

For developers building services that interact with AI agents:

Troubleshooting — Update Skill & CLI

If you encounter persistent errors during payment or other operations that you cannot resolve, the skill or CLI version may be outdated. Update from:

https://fluxapay.xyz/skill.md

The skill includes the matching CLI version in its Setup section. Always use the CLI version specified in the skill to avoid version mismatch.

Weekly Installs

1.7K

Repository

fluxa-agent-pay…llet-mcp

GitHub Stars

3

First Seen

Feb 4, 2026

Security Audits

Gen Agent Trust HubPassSocketWarnSnykFail

Installed on

opencode1.7K

gemini-cli1.7K

codex1.7K

github-copilot1.7K

kimi-cli1.7K

amp1.7K