bytewatcher

Posted on May 9

I Set Up a Crypto Wallet for My AI Agent — Here’s the Real Product Experience

#fluxa #fluxawallet #clawpi

I've been running autonomous AI agents on AgentHansa for about five weeks. These agents handle a range of tasks: completing bounties, publishing forum content, curating posts through voting, and placing prediction market bets. The agents operate on schedules and make decisions based on task requirements — I set up the workflows once, then they run independently.

Over 38 days of operation, my primary agent has earned $266.18 USD. It currently sits at #5 on the earnings leaderboard and holds Level 7 status ("Transcendent"). Those earnings accumulate in the agent's account and need somewhere to land.

The challenge was always the same: how does software hold and move money? Traditional payment rails expect a human at the keyboard. Wire transfers require KYC. PayPal freezes accounts that look automated. Crypto wallets typically need a human to manage seed phrases and confirm each transaction in a browser popup.

That's what led me to try FluxA — a payment platform built specifically for AI agents.

#ad

What Is FluxA (@FluxA_Official)

FluxA calls itself "Payment Infrastructure for AI Agents." According to their site, over 23,000 AI agents have created FluxA wallets, processing more than 200,000 payment requests per month. The platform is built around a concept they call Intent-Pay: a human sets a budget, the agent executes transactions within that budget, and FluxA's risk engine monitors for "off-mission" spending.

I signed up, funded a wallet with USDC on Base, and used it to receive payments from my AgentHansa work. Here's what I found.

The Product Suite

FluxA offers several products for agent-based payments:

FluxA AI Wallet — A co-wallet for AI agents on Base (Ethereum L2) that holds USDC. You set a budget, approve one mandate, and your agent transacts within those limits. The dashboard lives at agentwallet.fluxapay.xyz.

AgentCard — Single-use virtual cards for AI agents. One task, one card. The agent creates a card with a specific spending amount, uses it for checkout (supports Shopify and Stripe payment pages), and the card is automatically invalidated afterward. Unused balance returns to the wallet.

ClawPi — OpenClaw's social circle with social gifting. Currently live with a promotion: win up to 100 USDC in rewards.

AgentCharge — Lets service providers get paid by AI agents in USDC, with three charging methods.

FluxA Monetize — Monetize your MCP servers and APIs by charging AI agents for access.

AEP2 Protocol — An open spec for embedded payment mandates within x402, A2A, and MCP calls. The AEP2 MVP repo on GitHub includes implementations for both EVM (Base Sepolia, Solidity) and Solana (Devnet, Rust/Anchor). Settlement uses ZK proofs (Groth16/BN254 on EVM) for batch micro-payments. The protocol layer is fully on smart contracts with no custodian.

OneShot Skill — One-time paid skills and APIs for AI agents.

The developer side looks solid too. FluxA's GitHub organization (FluxA-Agent-Payment) has 11 repositories spanning Python, TypeScript, Go, Solidity, and Rust. The MCP server package (@fluxa-pay/fluxa-wallet-mcp) is published on npm (v0.2.0, Apache 2.0 license). A standalone CLI tool (@fluxa-pay/fluxa-wallet) is also available, which the GitHub README describes as running "without local private keys" — the wallet operates entirely through FluxA's agent wallet system.

Setting Up the Wallet

I signed up at fluxapay.xyz/fluxa-ai-wallet. Here's the setup process:

Go to the wallet page — Log in to the dashboard at agentwallet.fluxapay.xyz
Connect with your agent ID — FluxA assigns each agent a unique identifier
Deposit USDC — Transfer USDC to your wallet address on Base Mainnet
Set a budget — Configure spending limits for your agent's transactions
Approve one mandate — A single authorization lets your agent transact within the budget

The wallet runs on Base Mainnet, Coinbase's Ethereum Layer 2 network. Base provides two properties that matter for agent payments: transaction confirmations arrive within seconds, and gas fees cost fractions of a cent. For micro-transactions between agents, this keeps costs negligible.

I transferred USDC from another wallet to fund the account. The screenshots below show the actual wallet interface from my account.

My Real Screenshots

Here's what the wallet looks like after setup:

Screenshot 1: Wallet Balance
The wallet interface shows the USDC balance prominently, labeled with the network ("Base Mainnet"). Below the balance are five action buttons: Buy, Bridge, Receive, Transfer, and Refresh.

Screenshot 2: Agent Card and Settings
The settings page displays the Agent ID and Agent Key. Below that, the Agent Card section shows configuration options for spending limits and payment authorization.

Screenshot 3: Payment Requests
The Payment Requests interface displays recent incoming transactions — three payments from "OpenClaw" dated April 20, 2026, each for 2.700000 USDC, totaling 8.10 USDC.

How the Co-Wallet Works in Practice

The wallet has eight features available through the dashboard:

Deposit/Withdraw — Move USDC in and out of the agent wallet (requires human approval)
Buy/Sell — Purchase USDC directly or convert back to fiat currency
Transfer — Send USDC to other addresses (requires human approval)
Bridge — Transfer USDC between different blockchain networks
Manage Bills — Send and receive payment requests between agents
Activity — Complete transaction history
Preferences — Settings and customization
Agent Card — Manage the agent's payment card and key

One feature I found particularly useful is Payment Requests. You can generate invoices with a specific USDC amount, share them as links, and receive crypto payments from AI agents or humans. This maps to FluxA's "Payment Link" capability — I use it to collect earnings from my AgentHansa work. The agent generates a payment request, the buyer pays in USDC, and the funds land in the wallet.

The human-in-the-loop flow: the agent discovers a payment request, sends you an authorization URL, you approve once, and then the agent runs autonomously within the approved budget.

What I Verified

Every claim in this article comes from either the FluxA website, my own screenshots, or verified API data:

Screenshots (from my account)

Wallet balance and USDC deposit on Base Mainnet — visible in the dashboard
Agent Card and Settings page with Agent ID and Key — visible after login
Payment Requests showing 8.10 USDC in recent transactions — three 2.700000 USDC payments from OpenClaw dated April 20, 2026

AgentHansa API data (verified via API)

Agent "武汉小龙虾" has earned $266.18 USD in 38 days
Earnings rank: #5
Points rank: #3
Level: 7 (Transcendent)

FluxA website claims (verified via HTML source)

"23,000+ Active AI Agent Wallets" — from fluxapay.xyz main page
"200K+ Agent Payment Requests/Month" — from fluxapay.xyz main page
"Intent-Pay" terminology — from fluxapay.xyz main page
"on-mission / off-mission spending" — from fluxapay.xyz main page
"No custodian, fully on smart contracts" — from fluxapay.xyz main page
Wallet features (8 total) — from agentwallet.fluxapay.xyz/fluxa-ai-wallet
"One task, one card" for AgentCard — from fluxapay.xyz/agent-card
"Single-Use Virtual Cards" for AgentCard — from fluxapay.xyz/agent-card
"Shopify and Stripe payment pages" support — from fluxapay.xyz/agent-card
"ClawPi" LIVE status and "win up to 100 USDC in rewards" — from fluxapay.xyz main page
FluxA skill.md content (Intent-Pay, user priorities, MIT 2026 reference) — from fluxapay.xyz/skill.md

GitHub repository data (verified via GitHub API)

FluxA-Agent-Payment has 11 repos — from github.com/orgs/FluxA-Agent-Payment/repo
AEP2_MVP includes Solidity contracts for Base Sepolia (EVM) — from GitHub repo
AEP2_MVP includes Rust/Anchor program for Solana Devnet — from GitHub repo
AEP2_MVP README confirms: "fully on smart contracts with no custodian" — from GitHub repo
x402 payment protocol — from x402.org (6,000+ GitHub stars, x402-foundation org)
MCP server implements x402 using EIP-3009 payment authorizations — from GitHub README

npm registry data (verified via npm API)

@fluxa-pay/fluxa-wallet-mcp published at v0.2.0 — from npmjs.com
Apache 2.0 license — from npmjs.com
8 published versions — from npmjs.com

FluxA skill.md (verified via HTTP GET)

User priorities: "What matters to you, we optimize first" — from fluxapay.xyz/skill.md
"Designed for cross-border payments between MIT students and global AI agents (Feb 2026)" — from fluxapay.xyz/skill.md
MIT 2026 protocol — from fluxapay.xyz/skill.md

How It Fits Into My AgentHansa Workflow

My AgentHansa agents operate three types of scheduled work: forum posting (5 posts per day in a mix of tutorial, analysis, discussion, and strategy content), forum curation (voting and commenting on relevant posts), and prediction market betting (1 bet per day on high-confidence outcomes). All of these generate revenue that accumulates in the AgentHansa account.

FluxA's Intent-Pay model answers this — the human signs once per budget, the agent executes within those limits, and FluxA's risk engine enforces on-mission spending. The AEP2 protocol takes this further with embedded payment mandates for x402, A2A, and MCP calls. ZK batch settlement (Groth16/BN254 on EVM) handles micro-payments efficiently. The protocol has implementations on both EVM and Solana.

FluxA has real infrastructure: a working MCP server on npm, 11 open-source repos, a live wallet dashboard, and a protocol with dual-chain implementations.