FAQ

This page covers common questions that come up when using the FluxA Wallet Dashboard and the Integration tab. If something feels off, there’s a good chance it’s one of these.

Wallet & funds

Q: How long after topping up will my balance show?

Card / Google Pay top‑ups usually appear almost immediately. If you just completed a Buy flow, wait a few seconds and refresh the page. For on‑chain deposits via Add, wait for the transaction to confirm on‑chain before expecting the balance to update.

Q: How do I withdraw funds from FluxA?

On the Home page, click Transfer. In the modal, enter the destination address (must be Base Mainnet address) and amount, then click Send. If the transaction succeeds, you’ll see it in the Transactions list.

Q: What if a transfer fails?

First, double‑check that the destination address is a valid 0x... address and the amount is greater than zero. If errors persist, try again later and, if necessary, inspect the target network’s status in a block explorer.

Agent & policy

Q: I lost my AgentID / Token / JWT. What should I do?

If your agent uses the CLI or the MCP server, the credentials are stored locally in ~/.fluxa-ai-wallet-mcp/config.json (or in FLUXA_DATA_DIR if you set it), and fluxa-wallet status shows the configured Agent ID. If they are truly lost, register a new agent (fluxa-wallet init, or POST /register over HTTP), link it to your wallet again, and revoke the old agent under AI Agents to avoid confusion.

Q: What happens when I revoke an agent?

When you click Revoke access in an agent’s detail view and confirm, that agent can no longer initiate new payments. Existing transaction history remains visible, but any new payment request from that agent will be rejected.

Q: Automatic payments are failing even though the agent exists. Could this be policy‑related?

Often it is. Open the agent’s details and review the x402 Payment Policy section:

• make sure there is a policy for the host you’re testing against, and
• check that the monthly limit, per‑transaction limit, daily count, and minimum interval all permit the payment you’re attempting.

If the payment is stricter than your policy, try loosening those limits slightly and test again.

Integration

Q: Quick start doesn’t complete, and I see request or payment errors.

Work through these checks in order:

• Confirm the Home balance shows enough USDC (greater than zero).
• Make sure you’re logged into the expected FluxA account.
• Run fluxa-wallet --version and make sure the CLI is up to date (npm install -g @fluxa-pay/fluxa-wallet@latest).
• Run fluxa-wallet check-wallet. If linked is false, run fluxa-wallet link-wallet and open the URL.
• Run fluxa-wallet mandates and check that a signed mandate with enough remaining budget exists. If not, approve the authorizationUrl the agent gave you.
• If errors persist, reinstall the skill from https://fluxapay.xyz/skill.md.

Q: Local MCP is configured, but my client doesn’t show FluxA tools.

A few things to verify:

• The client config file was saved and the JSON is valid.
• You restarted the client after changing its configuration (Claude Desktop, Claude Code, etc.).
• MCP support is enabled in the client if it offers a toggle or flag.

If tools still don’t appear, run npx -y @fluxa-pay/fluxa-wallet-mcp@latest in a terminal to check that Node.js 18+ can start the server, and see MCP Server.

Q: Is there a hosted (remote) MCP endpoint?

No. The FluxA MCP server runs locally over stdio. For agents that can run shell commands, the fluxa-agent-wallet skill with the CLI is the recommended option. Hosted backends can call the HTTP API directly.

Q: Should my agent use the Skill, the CLI, MCP or the HTTP API?

• Skill + CLI (recommended): any agent that can run shell commands. Covers every feature.
• MCP: clients that support MCP tools but not shell commands. Covers a subset: Agent ID, mandates, x402, payouts and payment links (MCP Tools).
• HTTP API: backends and custom agent runtimes (API Guide).

Q: My curl calls from the API Guide fail. How can I debug them?

Start by making the requests verbose:

curl -v -X POST ...

Then, check:

• the HTTP status code (401, 403, 500, etc.),
• any error message in the response body,
• whether the Authorization header contains a valid bearer JWT, and
• whether the JSON body is complete and all field names are spelled correctly.

These clues will usually point to missing auth, mis‑typed field names, or an invalid request body.