# Integration notes — FluxA Agent Wallet + TaskMarket

## Target and scope

Target: **FluxA Agent Wallet**, the wallet surface at [agentwallet.fluxapay.xyz](https://agentwallet.fluxapay.xyz/) with the public FluxA wallet skill documentation available in the host environment. TaskMarket is the external worker market described by [taskmarket.dev](https://taskmarket.dev/) and its [CLI/API documentation](https://docs.taskmarket.dev/reference/cli).

This artifact is a companion MCP server and agent skill, not a claim of a merged change inside FluxA's proprietary wallet application. It is intentionally useful as a drop-in integration for an agent runtime that already uses FluxA as its wallet approval boundary.

## Why the target is relevant

FluxA is the user's Base-USDC agent wallet. The wallet is the correct place to preserve spending limits and human approval. TaskMarket is a competitive worker market with public tasks, submissions, and paid acceptance actions. Connecting discovery and review to the wallet boundary lets an agent offer delegation without silently signing or funding a task.

## Evidence that this is not an existing TaskMarket integration

The public FluxA wallet surface and its published wallet capability documentation expose wallet balances, transfers, payment links, and x402/market capabilities; they do not expose a TaskMarket discovery, submission-review, or delegation tool. The implementation therefore adds a separate, clearly named MCP adapter rather than pretending an upstream FluxA feature exists.

## Implemented flow

1. `taskmarket_list_open_tasks` discovers open tasks and reward/deadline metadata.
2. `taskmarket_inspect_task` reads available actions and flags any action that would require payment.
3. `taskmarket_prepare_delegation` creates a local draft with `status: draft_requires_user_authorization`.
4. `taskmarket_list_submissions` exposes a review queue; the adapter never accepts or rejects work automatically.

The adapter has no private-key handling, no signing code, no USDC transfer code, and no network write path. Any later funding or acceptance must happen through a separate wallet-aware flow after fresh user authorization.

## Reproduction and status

- Source: [`taskmarket-fluxa-delegation.mjs`](./taskmarket-fluxa-delegation.mjs)
- Skill guide: [`taskmarket-fluxa-skill.md`](./taskmarket-fluxa-skill.md)
- Smoke evidence: [`taskmarket-fluxa-demo.json`](./taskmarket-fluxa-demo.json)
- Public demo host: [CashForge Evidence Desk](https://cashforge-evidence-desk.marielramos473.chatgpt.site/)
- Validation: Node syntax check, MCP handshake test, and rendered-site tests all pass.
- Status: submitted/open companion integration; upstream merge is not claimed.