{ "data": { "a": { "slug": "fluxa-ai-wallet", "name": "FluxA AI Wallet", "vendor": "FluxA Technology Pte. Ltd.", "vendorUrl": "https://fluxapay.xyz", "kind": "http-api", "category": "agent-wallets", "summary": "FluxA AI Wallet is a hosted agent wallet from FluxA Technology that signs x402 (EIP-3009) USDC payments on Base within budgets a person approves, reached through the fluxa-wallet CLI, a stdio MCP server and agent skills.", "url": "https://www.anchorterminal.com/tools/fluxa-ai-wallet", "markdownUrl": "https://www.anchorterminal.com/tools/fluxa-ai-wallet.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/fluxa-ai-wallet.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/fluxa-ai-wallet.json", "dns": "fluxa-ai-wallet.grade.anchorterminal.com", "repo": "https://github.com/FluxA-Agent-Payment/FluxA-AI-Wallet-MCP", "license": "The CLI and MCP server source is Apache-2.0 (LICENSE file and both package.json files), though the README's last section says MIT. The hosted wallet service is closed, and no terms covering the wallet were found", "transports": [ "http", "stdio" ], "remoteUrl": "https://walletapi.fluxapay.xyz", "packages": [ { "registry": "npm", "name": "@fluxa-pay/fluxa-wallet" }, { "registry": "npm", "name": "@fluxa-pay/fluxa-wallet-mcp" } ], "auth": "mixed", "authNotes": "An agent connects with `fluxa-wallet connect` (or the MCP tool `connect_wallet`), which returns an `authorization_url` on agentwallet.fluxapay.xyz for the owner to approve in a browser. The claim returns an Agent ID, a token and an RS256 JWT, stored in `~/.fluxa-ai-wallet-mcp/config.json` (mode 0600) or injected as `AGENT_ID`, `AGENT_TOKEN` and `AGENT_JWT`. The owner picks the token's validity (1h, 24h, 7d, 1mo, 180d or 1y; the server suggests 180 days locally and 7 days in cloud or container environments), and the JWT is refreshed with the token. `token_expired` and `token_revoked` return `reconnect_required`. The legacy `init` registers an Agent ID with an unauthenticated `POST https://agentid.fluxapay.xyz/register`. Spending needs a mandate the owner signs in the browser. AgentMarket commands can instead use `fxa_live_` keys with a spend limit, revocable from the CLI.", "pricing": "usage", "pricingNotes": "No fee schedule for the wallet, x402 signing, payouts, payment links or refunds was found in the repository, the skills or the AgentMarket pricing, terms and llms.txt pages (checked 2026-11-07). Merchants set x402 prices. Agent card products list their fees through `fluxa-wallet card types`, which needs a connected wallet, so those fees were not read. The wallet site and docs at agentwallet.fluxapay.xyz and docs.fluxapay.xyz could not be read, so whether opening a wallet needs a card is unchecked. AgentMarket's Balance is $1 = 1 Balance, with Units bundles from $1 to $25.", "priceSummary": "Pay per use", "where": "both", "x402": { "level": "partial", "evidence": "The wallet signs x402 `exact` (EIP-3009) payment authorisations for USDC on Base and Base Sepolia as a buyer (`fluxa-wallet x402 --mandate \u003cid\u003e --payload \u003c402 body\u003e`, MCP `request_x402_payment` and `request_x402_v3_payment`), and its payment links can be paid over x402 so another agent can pay the holder (https://github.com/FluxA-Agent-Payment/FluxA-AI-Wallet-MCP/blob/main/skills/fluxa-agent-wallet/INTEGRATION-GUIDE-CHARGE-AGENT.md, checked 2026-11-07). FluxA's own wallet API is not paid over x402, MPP or L402.", "endpoints": [] }, "toolCount": 15, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://docs.fluxapay.xyz/", "capabilities": [ "payments.x402", "wallet.spend-limits", "wallet.onchain", "payments.card", "auth.agent-identity" ], "tags": [ "hosted", "official", "open-source", "apache-2.0", "cli", "mcp", "stdio", "skills", "typescript", "wallet", "x402", "stablecoins", "virtual-cards", "usdc", "base" ], "lastRelease": "2026-11-06", "graded": true, "anchor": { "graded": true, "score": 47, "grade": "D", "agentReady": false, "rank": 1164, "ranked": true, "rankOf": 1513, "categoryRank": 11, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 60, "maintenance": 66, "payments": 45, "reliability": 20, "schema": 61, "security": 52, "transparency": 32 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "low", "date": "2026-11-07" }, "negative": 0, "verdict": "Every spend runs against a mandate the owner signs in a browser, with a budget, a validity window and an optional host allowlist, and payouts need approval or a mandate. The published MCP package is 0.2.0 from March 2026 against 0.6.0 in the repository, and no status page, fee schedule, wallet terms or custody statement was found.", "bestFor": "An agent in a CLI-capable client that needs to pay x402 APIs, send USDC on Base or receive payments through links, inside budgets a person signs.", "strengths": [ "Spending runs against owner-signed mandates with a limit, a validity window and an optional host allowlist, enforced by the wallet API", "Payouts need per-payout browser approval unless a signed mandate is passed, and a required `payout_id` makes repeats return the same payout", "The CLI returns JSON with error codes, `next_command` hints and `retryable` and `reconnect_required` flags", "Client source is public under Apache-2.0, with 25 CLI releases on npm since March 2026, the latest on 6 November 2026", "Payment links let another agent pay the holder over x402, and refunds of link payments are supported" ], "weaknesses": [ "The published MCP package is 0.2.0 from 2 March 2026 with 13 tools, while the repository says 0.6.0 with 15", "No status page, rate limit, SLA, fee schedule or security contact was found", "Who holds the wallet keys is not stated. The docs say FluxA Wallet signs and call it managed", "The only terms and privacy policy read are AgentMarket's, which do not mention the wallet, cards, KYC or payouts", "The skill steers agents to paid APIs over free search and to request budgets for at least 100 calls by default" ], "agentNotes": [ "Run `fluxa-wallet status` first. If `configured` and `wallet_linked` are true, skip `connect`; otherwise show the `authorization_url` and wait with `connect-status --wait 100`", "On `token_expired` or `token_revoked`, reconnect with the same `--agent-id`. Never run `init` to recover, which creates a new identity", "Pass a unique `--id` on every `payout` and reuse it on retry; a repeat returns the existing payout instead of paying twice", "Check `fluxa-wallet mandates` for a signed mandate with enough remaining budget before creating one, and size new budgets to the task", "Install the CLI from npm, not the MCP package, whose npm release 0.2.0 lacks `connect_wallet` and `get_wallet_connection`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "low", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47 } ], "editorialScores": { "ergonomics": 60, "maintenance": 66, "payments": 45, "reliability": 20, "schema": 61, "security": 52, "transparency": 26 }, "provenanceScore": 38, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @fluxa-pay/fluxa-wallet" }, "letme": { "capability": "https://letme.dev/payments.x402", "tool": "https://letme.dev/fluxa-ai-wallet" }, "sameCompany": [ "fluxa-agentmarket" ], "area": "payments", "provenance": { "legalEntity": "FluxA Technology Pte. Ltd.", "domain": "fluxapay.xyz", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "", "changelog": "", "securityTxt": "unknown", "checked": "2026-11-07", "notes": [ "The legal entity is from the footer of agentmarket.fluxapay.xyz, \"© 2025 FluxA Technology Pte. Ltd. All rights reserved.\", the same on the about, terms, privacy and pricing pages. No registration number, address or country is given on those pages. A web search result names a companieshouse.sg page for FluxA Technology Pte Ltd with UEN 202555700C; that host could not be fetched, so the register entry is unread.", "AgentMarket's terms (effective 14 January 2026) and privacy policy (updated 14 January 2026) describe the marketplace and its Balance and do not mention the Agent Wallet, cards, KYC or payouts, so they are not recorded as the wallet's terms. The terms name no entity in their text and no governing law; contact support.fluxapay@fluxapay.xyz.", "fluxapay.xyz, agentwallet.fluxapay.xyz and docs.fluxapay.xyz could not be read. Each robots.txt fetch was refused for want of an approval on 7 November 2026, so nothing on those hosts was fetched. The wallet's own terms, privacy policy, fees, security.txt and docs are unchecked.", "https://agentmarket.fluxapay.xyz/.well-known/security.txt answered a client error. The repository has no SECURITY.md.", "The wallet API, Agent ID API and approval pages are on fluxapay.xyz subdomains named in the CLI source. agentmarket.fluxapay.xyz's robots.txt allows / and disallows /api/ (except /api/discover and /api/llm/skills.md) and /console/; nothing disallowed was fetched.", "unchecked: RDAP for fluxapay.xyz, the MCP registry, the Wayback Machine, GitHub stars and issues (the GitHub API refused the session) and npm download counts." ], "score": 38 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/fluxa-ai-wallet.json", "live": { "slug": "fluxa-ai-wallet", "probe": { "target": "https://walletapi.fluxapay.xyz", "method": "get", "lastAt": "2026-11-08T14:47:50.695700215Z", "lastOk": true, "lastStatus": 404, "lastMs": 532, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 542, "p95ms24h": 603, "samples24h": 90, "samples30d": 90, "days": [ { "date": "2026-11-08", "probes": 90, "ok": 90 } ], "since": "2026-11-08T00:00:00Z" }, "updatedAt": "2026-11-08T14:47:50.695700215Z" }, "streak": { "days": 0, "from": "2026-11-08", "sinceWatching": true, "best": 0 } }, "answer": "Payman Genie MCP and FluxA AI Wallet score within a point of each other on agent readiness, 47.2 (D) and 47 (D). FluxA AI Wallet leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "b": { "slug": "payman", "name": "Payman Genie MCP", "vendor": "Payman AI", "vendorUrl": "https://paymanai.com", "kind": "http-api", "category": "payment-platforms", "summary": "Banking and payment tools for agents. Its Genie MCP server supports bill payments, cards, transfers and other transactions within owner-defined limits.", "url": "https://www.anchorterminal.com/tools/payman", "markdownUrl": "https://www.anchorterminal.com/tools/payman.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/payman.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/payman.json", "dns": "payman.grade.anchorterminal.com", "repo": "https://github.com/PaymanAI/genie-mcp-stdio", "license": "MIT", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://genie.paymanai.com/mcp", "packages": [ { "registry": "npm", "name": "@paymanai/genie-mcp-stdio" } ], "auth": "oauth", "authNotes": "OAuth 2.1 authorisation code with S256 PKCE as a public client, scopes `genie:ask` and `genie:self`; the first call answers 401 with resource metadata. Clients can now register dynamically with exact redirect URIs and no secret; the stdio bridge is a preregistered native client that stores a rotating refresh token (90 days from last use) in a 0600 file and revokes it on logout. Access tokens last an hour. No API keys for people; integration keys exist for organisations acting for customers.", "pricing": "paid", "pricingNotes": "No price list is published for Genie, and signing up needs no card or bank details. Fees from connected providers (card issuers, Coinbase, banks) still apply. The bank product is sold through demos only (https://genie.paymanai.com/developers).", "priceSummary": "Paid", "where": "both", "x402": { "level": "partial", "evidence": "Genie can pay x402-protected APIs from a daily agent budget the owner sets. Payman doesn't offer a way to accept x402 payments (https://genie.paymanai.com/).", "endpoints": [] }, "toolCount": 5, "popularity": { "githubStars": 0, "npmWeekly": 33, "pypiWeekly": null, "asOf": "2026-09-30" }, "docsUrl": "https://genie.paymanai.com/developers", "capabilities": [ "payments.x402", "payments.card", "payments.payouts" ], "tags": [ "hosted", "mcp", "x402", "no-card", "closed-source" ], "lastRelease": "2026-09-19", "graded": true, "anchor": { "graded": true, "score": 47.2, "grade": "D", "agentReady": false, "rank": 1160, "ranked": true, "rankOf": 1513, "categoryRank": 13, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 68, "maintenance": 30, "payments": 35, "reliability": 25, "schema": 56, "security": 80, "transparency": 46 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -3, "negativeNotes": [ "-3, same-day change. Genie renamed its OAuth scope from `yuki:ask` to `genie:ask` with no compatibility window, so the published 0.2.x bridge (tags v0.2.0 and v0.2.1) was refused by the server. The only notice is the bridge's 18 September 2026 commit that followed it (https://github.com/PaymanAI/genie-mcp-stdio/commit/e52921d5f7067dec5270731abe8ec65e2b02b714)" ], "verdict": "OAuth 2.1 with PKCE, two scopes, one-hour access tokens and refresh tokens rotated on every use and revoked on logout. No published pricing, status page, rate limits or changelog.", "bestFor": "A person or small business who wants an assistant to pay bills, issue one-time cards or pay x402 APIs within hard limits.", "strengths": [ "OAuth 2.1 with PKCE, two scopes, one-hour access tokens and refresh tokens rotated on every use and revoked on logout", "Owner-set per-payment, daily and monthly limits and approved payees, with code or passkey approval over a threshold", "Five documented statuses and three retry codes tell an agent when to stop and when retrying is safe", "Five compact MCP tools, one of which moves money", "Genie holds no funds; money stays at the bank, card wallet or Coinbase" ], "weaknesses": [ "No published pricing, status page, rate limits or changelog", "Pays x402 APIs but can't accept x402, MPP or any agent payment", "docs.paymanai.com failed with a Cloudflare 526 and the payman-ts SDK hadn't shipped since September 2025, with no deprecation notice (1 October check)", "The privacy policy allows anonymised or aggregated data to train AI models", "No tagged bridge release since v0.2.1 on 14 September 2026, and no repository CI" ], "agentNotes": [ "Pass the person's request to `ask_genie` in their own words; don't pick accounts or fill payment fields", "On `needs_approval`, stop and tell the person; approval happens in their Genie account", "Retry only after `NOTHING_RAN` or `BUSY`, never after `OUTCOME_UNKNOWN`", "Treat `done` as acted, not settled; check the activity history before confirming a payment", "Sign-ins from bridge 0.3.x lack `genie:self`; log out and sign in again to use the self-service tools" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 47.2 } ], "editorialScores": { "ergonomics": 68, "maintenance": 30, "payments": 35, "reliability": 25, "schema": 56, "security": 80, "transparency": 33 }, "provenanceScore": 59, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http genie https://genie.paymanai.com/mcp", "config": { "mcpServers": { "genie": { "args": [ "-y", "@paymanai/genie-mcp-stdio" ], "command": "npx" } } } }, "letme": { "capability": "https://letme.dev/payments.x402", "tool": "https://letme.dev/payman" }, "area": "payments", "provenance": { "legalEntity": "Payman AI, Inc.", "domain": "paymanai.com", "domainRegistered": "2024-04-12", "endpointOnVendorDomain": true, "terms": "https://paymanai.com/terms-of-use", "privacy": "https://paymanai.com/privacy-policy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-11-04", "notes": [ "Terms of Use last updated 2026-11-01. They define the Service to include the website and APIs and bar using \"any data mining, robots, scraping, or similar data gathering methods\" (https://paymanai.com/terms-of-use)", "API licence agreement updated 2026-09-29, per the 30 September check (https://paymanai.com/api-license)", "Trust centre at https://trust.paymanai.com/ claims SOC 2, per the 30 September check", "Privacy policy and security.txt per the 30 September check, not re-read on 2026-11-04" ], "score": 59 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/payman.json", "live": { "slug": "payman", "probe": { "target": "https://genie.paymanai.com/mcp", "method": "get", "lastAt": "2026-11-08T14:48:04.480456011Z", "lastOk": true, "lastStatus": 401, "lastMs": 271, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 288, "p95ms24h": 397, "samples24h": 242, "samples30d": 7844, "days": [ { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 150, "ok": 150 } ], "since": "2026-10-08T00:00:00Z" }, "versions": [ { "registry": "npm", "name": "@paymanai/genie-mcp-stdio", "version": "0.4.0", "seenAt": "2026-11-08T01:26:23.374464932Z" } ], "githubStars": 0, "npmWeekly": 8, "securityTxt": { "url": "https://paymanai.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:33.317721554Z" }, "domain": { "domain": "paymanai.com", "registered": "2024-04-12", "source": "https://rdap.verisign.com/com/v1/domain/paymanai.com", "checkedAt": "2026-11-08T14:37:27.624966624Z" }, "pages": [ { "url": "https://paymanai.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:16:08.078438599Z", "changedAt": "2026-10-16T22:28:21.648652728Z", "fingerprint": "cbb8fa9fe125" }, { "url": "https://paymanai.com/terms-of-use", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:16:10.162280198Z", "changedAt": "2026-10-15T21:31:41.070305773Z", "fingerprint": "654a3372b383" } ], "mcpTools": { "url": "https://genie.paymanai.com/mcp", "checkedAt": "2026-11-08T02:00:33.613164337Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:46:46.214992804Z" }, "github": { "repo": "paymanai/genie-mcp-stdio", "checkedAt": "2026-11-02T09:15:11.176070714Z", "stars": 0, "archived": false, "issuesEnabled": true, "pushedAt": "2026-09-19T04:26:24Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 2 }, "updatedAt": "2026-11-08T14:48:04.480456011Z" }, "streak": { "days": 31, "from": "2026-10-08", "sinceWatching": true, "best": 31 } }, "edges": [ { "by": 36, "category": "maintenance", "leads": "fluxa-ai-wallet", "name": "Maintenance \u0026 community", "reasons": { "a": "`@fluxa-pay/fluxa-wallet` 0.6.0 was published on 6 November 2026, one day before this check (30). Eight CLI releases since 10 August 2026, among them 0.5.2 on 14 October, 0.5.3 on 25 October and 0.5.6, 0.5.7 and 0.6.0 between 3 and 6 November (20). The repository merged 43 pull requests, all from the organisation's own branches, and commits run weekly. Issues and outside pull requests could not be read because the GitHub API refused the session. Discord and a support address are linked from AgentMarket and were not tested (8 of 25). Graded as an API, the line asks for current official SDKs. The CLI is current, but there is no SDK library and the MCP package on npm has not been published since 2 March 2026 (5 of 15). 68 node:test cases exist with no CI workflow, neither npm package declares its repository, and the MCP package's last release lags the source by eight months (3 of 10). Total 66.", "b": "The bridge's newest tagged release is v0.2.1 (14 September 2026), 51 days before 4 November (20). Since 6 August the repository has two tagged releases, v0.2.0 and v0.2.1, both on 14 September; the 0.3.0 and 0.4.0 version bumps of 18 September carry no tag or changelog entry, so they don't count as releases, and no commit has landed since 18 September (0). Two merged pull requests and no changelog. The older developer platform looks abandoned, with docs.paymanai.com failing on a Cloudflare 526 and the payman-ts SDK last released on 18 September 2025, per the 1 October check, not re-read on 4 November (5). No current SDK, and the official MCP registry wasn't read first-hand (0). A Node test suite with a fake authorisation server, but no CI workflow in the repository (5). 20+0+5+0+5 = 30." }, "scores": { "a": 66, "b": 30 } }, { "by": 28, "category": "security", "leads": "payman", "name": "Security \u0026 auth", "reasons": { "a": "The agent holds an Agent ID, a token whose validity the owner picks from 1 hour to 1 year at browser approval, and a short-lived RS256 JWT refreshed from the token; `token_revoked` exists. Credentials sit in a 0600 JSON file or environment variables. The token is not scoped, since limits live in mandates, and legacy `init` tokens are described as not expiring. Agent VCs are audience-bound and rejected by FluxA's own endpoints. No secret travels in a URL (22 of 30). Every x402 payment needs a mandate the owner signs, with a limit, a validity and an optional host allowlist enforced by the wallet API, payouts need per-payout approval unless a mandate covers them, cards need a mandate and KYC, and linked-card mandates are scoped to one merchant. A payout mandate sets no payee allowlist that was documented, and the skill tells agents to request budgets for at least 100 calls by default (16 of 20). The wallet returns little third-party content itself, but the skill sends agents to third-party x402 APIs, ClawPI posts and a remote announcement.md with no guidance on treating them as untrusted, its description steers agents to paid APIs even when a free web search looks enough, and the daily check-in runs `npx -y @fluxa-pay/fluxa-wallet@latest` unpinned twice a day (4 of 15). `mandates` lists limit, spent and remaining, with `recent-transactions`, `received-records` and payout status by CLI, and the MCP server writes a local audit log; the wallet app's logs were not read (10 of 15). No SECURITY.md, disclosure policy, bug bounty or certification was found, and agentmarket.fluxapay.xyz has no security.txt; fluxapay.xyz's is unchecked (0 of 20). Total 52.", "b": "OAuth 2.1 with S256 PKCE, scopes `genie:ask` and `genie:self`, one-hour access tokens, refresh tokens rotated on every use and revoked through RFC 7009 on logout. Dynamic client registration is now documented (30). The owner sets per-payment, daily and monthly limits and approved payees, payments over an ask-me threshold need a six-digit code or passkey, and approvals happen in Genie, never in the chat. The assistant can grant itself read access only, and full access needs the owner (20). The agent passes the person's words to another agent; limits and out-of-band approval sit behind it, but we found no prompt-injection guidance as such (10). Genie says every decision is logged in an activity history (12). \"AICPA SOC 2 certified\" on the site and a Vanta trust centre we couldn't render, no security.txt per the 30 September check, and no disclosure policy or bug bounty found (8). No advisory for @paymanai/genie-mcp-stdio or any Payman package on osv.dev on 4 November. Genie holds no funds; money stays at the bank, card wallet or Coinbase, and we found no licence claim. The developer page, home page and trust centre readings are per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms). 30+20+10+12+8 = 80." }, "scores": { "a": 52, "b": 80 } }, { "by": 14, "category": "transparency", "leads": "payman", "name": "Transparency \u0026 trust", "reasons": { "a": "The CLI and MCP server source is Apache-2.0 per the LICENSE file and both package.json files, while the README's last section says MIT. The hosted wallet is closed, and no terms covering it were found. AgentMarket's terms describe only the marketplace (15 of 30). AgentMarket's privacy policy of 14 January 2026 names Stripe and model providers and gives no retention periods, and it does not mention wallet addresses, KYC profiles, card data or payouts, which the CLI collects or handles. The wallet's own privacy policy was unreachable (5 of 30). The README marks `init` and `link-wallet` as legacy but still supported, and the skill pins a minimum CLI version; no deprecation policy or dated notice was found (3 of 20). Stripe is the only provider named; no card issuer, KYC provider, custody provider or data location is named. The CLI and MCP code send no telemetry (3 of 20). Total 26.", "b": "Bridge under MIT, Genie closed under published terms (updated 1 November 2026) and an API licence (15). Privacy policy updated 21 September 2026 names Payman AI, Inc. in Durango, Colorado, gives no retention periods and no DPA, and says anonymised or aggregated data is used to train AI models (12). No deprecation notice for the old developer platform even though its docs no longer load (0). Stripe, Google and unnamed identity-verification and credit-bureau providers are named, with transfers \"including the United States\" (6). The privacy policy is per the 1 October check, not re-read on 4 November. 15+12+0+6 = 33." }, "scores": { "a": 32, "b": 46 } }, { "by": 10, "category": "payments", "leads": "fluxa-ai-wallet", "name": "Payments \u0026 pricing", "reasons": { "a": "Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. The wallet pays x402 as a buyer and its payment links can be paid over x402 so another agent pays the holder, as sponge-wallet's payment links were read. FluxA's own wallet API is not paid over x402, so the merchant step (25 of 40). No fee schedule for the wallet, x402 signing, payouts or payment links was found, and card fees appear only through an authenticated command (0 of 20). Registering an Agent ID and creating payment links cost nothing and need no card per the README and the charge-agent guide, but the wallet sign-up at agentwallet.fluxapay.xyz could not be read, so whether opening a funded wallet needs a card is unchecked (10 of 20). `POST https://agentid.fluxapay.xyz/register` returns credentials with no human step, but the CLI marks it legacy, the default connection needs a browser approval, and every spend needs the owner's wallet and a mandate signed in a browser (10 of 20). Total 45.", "b": "Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. Genie pays x402 APIs from a daily agent budget the owner sets, the buyer step (15 of 40). Payman has no way to accept x402 or MPP, and Genie itself isn't paid over either. No price list for Genie anywhere we looked (0). Free signup with no card or bank details (20). A person signs up and signs in through a browser (0)." }, "scores": { "a": 45, "b": 35 } }, { "by": 8, "category": "ergonomics", "leads": "payman", "name": "Agent ergonomics", "reasons": { "a": "The MCP server has 15 tools with about 4,700 characters of descriptions, the 11 to 30 band (15). The CLI path loads SKILL.md (26.5 KB) and one of 18 guides per task, about 112 KB in all, with no read-only subset (no add-back, 15 of 25). `card transactions` takes page, limit, type and a time range, refunds take limit and offset, `received-records` and `recent-transactions` take a limit up to 100, and `market search` can be scoped to models or vendors; no cursor (12 of 20). Errors carry a `code`, `retryable`, `reconnect_required` and a `next_command` or `next_tool`, and card errors map to recovery hints, but the CLI exits only 0 or 1 and the MCP payment tools return the wallet API's raw error body without `isError` (14 of 20). A required `payout_id` idempotency key, `--biz-id` dedup and `--request-id` continuation on card operations, and the skill says not to initiate again to retry a payment. No `readOnlyHint` or `destructiveHint` on any MCP tool (12 of 20). Base USDC is the default network and asset, mandates default to 8 hours and the CLI installs in one command, but there is no SDK library and both packages are TypeScript (7 of 15). Total 60.", "b": "One money tool and four small self-service tools (`get_genie_agent`, `rename_genie_agent`, `grant_genie_read_access`, `request_genie_access`) (25). Answers are natural-language messages with no size or filter controls (5). The `status` field (`done`, `needs_input`, `needs_approval`, `refused`, `error`) tells the agent what to do next (18). Retry rules separate safe and unsafe failures, and `done` is documented as not proof of settlement. We couldn't check tool annotations (12). One required parameter, but no SDK; Genie is MCP only, plus the stdio bridge (8). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026)." }, "scores": { "a": 60, "b": 68 } }, { "by": 5, "category": "reliability", "leads": "payman", "name": "Reliability", "reasons": { "a": "Graded with the hosted lines, because signing, mandates and approvals all run on FluxA's wallet API and the CLI and MCP server only wrap it, as kite-agent-passport and kane-cli were read. No status page was found in the repository, the skills or AgentMarket's pages. fluxapay.xyz and the wallet and docs hosts could not be read, so a status page there is unchecked and scored absent (0). With no readable history the record takes the default (5). No rate limit with numbers was found (0). The connection service treats 429 `slow_down` as wait and poll and marks errors `retryable`, the skill says a 503 means retry shortly, payouts require a caller-chosen `payout_id` that returns the existing payout on a repeat, `--biz-id` rejects a duplicate with 409, and card create and recharge resume with `--request-id` instead of paying again. No Retry-After or backoff schedule is documented for the wallet API (10 of 15). No SLA was found (0). No beta label was found on the wallet in what was read, but both packages are at 0.x, agent cards sit behind a waitlist and the wallet site was unread (5 of 10). Total 20.", "b": "No status page found for Genie or Payman (0), so no incident history to read (5). No rate limits published (0). The developer page says to retry an `error` only after `NOTHING_RAN` or `BUSY` and never after `OUTCOME_UNKNOWN`, which is safe-retry guidance for money-moving calls, but there's no 429 or Retry-After behaviour (12 of 15). No SLA (0). Genie is sold as a live product with no beta label, while the stdio bridge is at 0.4.0 (8 of 10). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026). 0+5+0+12+0+8 = 25." }, "scores": { "a": 20, "b": 25 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "FluxA Technology Pte. Ltd.", "b": "Payman AI", "name": "Vendor" }, { "a": "https://walletapi.fluxapay.xyz", "b": "https://genie.paymanai.com/mcp", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Pay per use", "b": "Paid", "name": "Pricing" }, { "a": "payer tooling only", "b": "payer tooling only", "name": "x402" }, { "a": "The CLI and MCP server source is Apache-2.0 (LICENSE file and both package.json files), though the README's last section says MIT. The hosted wallet service is closed, and no terms covering the wallet were found", "b": "MIT", "name": "Licence" }, { "a": "15", "b": "5", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "no", "name": "llms.txt" }, { "a": "2026-11-06", "b": "2026-09-19", "name": "Last release" }, { "a": "no document linked", "b": "2026-09-29", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-09-29", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "yes", "name": "Customer content may train models" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "0 stars, 33 npm/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Payman Genie MCP and FluxA AI Wallet score within a point of each other on agent readiness, 47.2 (D) and 47 (D). FluxA AI Wallet leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.", "question": "Which is better for AI agents, FluxA AI Wallet or Payman Genie MCP?" }, { "answer": "FluxA AI Wallet takes an API key or an OAuth sign-in. Payman Genie MCP uses an OAuth sign-in.", "question": "Do FluxA AI Wallet and Payman Genie MCP need an API key?" }, { "answer": "Yes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Payman Genie MCP at https://genie.paymanai.com/mcp.", "question": "Can an agent call FluxA AI Wallet and Payman Genie MCP without installing anything?" }, { "answer": "FluxA AI Wallet is open source (The CLI and MCP server source is Apache-2.0 (LICENSE file and both package.json files), though the README's last section says MIT. The hosted wallet service is closed, and no terms covering the wallet were found). No open-source release is listed for Payman Genie MCP.", "question": "Are FluxA AI Wallet and Payman Genie MCP open source?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 61 against 56", "Payments \u0026 pricing, 45 against 35", "Maintenance \u0026 community, 66 against 30" ], "also": [ "Open source", "No incidents deducted, where Payman Genie MCP loses 3 points for them" ], "goodFor": "An agent in a CLI-capable client that needs to pay x402 APIs, send USDC on Base or receive payments through links, inside budgets a person signs.", "slug": "fluxa-ai-wallet", "watchFor": "The published MCP package is 0.2.0 from 2 March 2026 with 13 tools, while the repository says 0.6.0 with 15" }, { "aheadOn": [ "Reliability, 25 against 20", "Agent ergonomics, 68 against 60", "Security \u0026 auth, 80 against 52", "Transparency \u0026 trust, 46 against 32" ], "also": [ "Free to start without a card" ], "goodFor": "A person or small business who wants an assistant to pay bills, issue one-time cards or pay x402 APIs within hard limits.", "slug": "payman", "watchFor": "No published pricing, status page, rate limits or changelog" } ], "history": { "fluxa-ai-wallet": null, "payman": [ { "causes": [ "correction" ], "date": "2026-11-04", "delta": -5.6, "from": 52.8, "fromGrade": "D", "to": 47.2, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.3, "from": 52.5, "fromGrade": "D", "to": 52.8, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.5, "from": 53, "fromGrade": "D", "to": 52.5, "toGrade": "D" } ] }, "job": { "capability": "payments.x402", "name": "x402 payments" }, "others": [ { "json": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-payman.json", "title": "Adyen MCP server vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/adyen-mcp-server-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/agentcard-vs-fluxa-ai-wallet.json", "title": "Agentcard vs FluxA AI Wallet", "url": "https://www.anchorterminal.com/compare/agentcard-vs-fluxa-ai-wallet" }, { "json": "https://www.anchorterminal.com/compare/crossmint-vs-payman.json", "title": "Crossmint API + Docs MCP vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/crossmint-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/lago-vs-payman.json", "title": "Lago vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/lago-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/orb-vs-payman.json", "title": "Orb vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/orb-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/paid-vs-payman.json", "title": "Paid vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/paid-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/payman-vs-skyfire.json", "title": "Payman Genie MCP vs Skyfire API + MCP", "url": "https://www.anchorterminal.com/compare/payman-vs-skyfire" }, { "json": "https://www.anchorterminal.com/compare/circle-wallets-vs-fluxa-ai-wallet.json", "title": "Circle Wallets (Agent Wallets, Programmable Wallets) vs FluxA AI Wallet", "url": "https://www.anchorterminal.com/compare/circle-wallets-vs-fluxa-ai-wallet" }, { "json": "https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-fluxa-ai-wallet.json", "title": "Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs FluxA AI Wallet", "url": "https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-fluxa-ai-wallet" }, { "json": "https://www.anchorterminal.com/compare/atxp-vs-payman.json", "title": "ATXP vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/atxp-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-ai-wallet.json", "title": "Circle Gateway Nanopayments vs FluxA AI Wallet", "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-ai-wallet" }, { "json": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-payman.json", "title": "Circle Gateway Nanopayments vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-fluxa-ai-wallet.json", "title": "FluxA AgentMarket vs FluxA AI Wallet", "url": "https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-fluxa-ai-wallet" }, { "json": "https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-payman.json", "title": "FluxA AgentMarket vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-kite-agent-passport.json", "title": "FluxA AI Wallet vs Kite Agent Passport", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-kite-agent-passport" }, { "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-nevermined.json", "title": "FluxA AI Wallet vs Nevermined API + MCP", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-nevermined" }, { "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-openfort.json", "title": "FluxA AI Wallet vs Openfort", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-openfort" }, { "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.json", "title": "FluxA AI Wallet vs Privy Wallets (server wallets, agent wallets, policy engine)", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy" }, { "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet.json", "title": "FluxA AI Wallet vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet" }, { "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets.json", "title": "FluxA AI Wallet vs Turnkey Agentic Wallets", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets" }, { "json": "https://www.anchorterminal.com/compare/nevermined-vs-payman.json", "title": "Nevermined API + MCP vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/nevermined-vs-payman" }, { "json": "https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.json", "title": "Payman Genie MCP vs Stripe API + MCP", "url": "https://www.anchorterminal.com/compare/payman-vs-stripe-mcp" }, { "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault.json", "title": "FluxA AI Wallet vs Agent Vault by Self", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault" } ], "panel": null, "scores": [ { "by": 5, "edge": "payman", "fluxa-ai-wallet": 20, "key": "reliability", "name": "Reliability", "payman": 25, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "fluxa-ai-wallet", "fluxa-ai-wallet": 61, "key": "schema", "name": "Schema \u0026 documentation", "payman": 56, "weight": 13 }, { "by": 8, "edge": "payman", "fluxa-ai-wallet": 60, "key": "ergonomics", "name": "Agent ergonomics", "payman": 68, "weight": 13 }, { "by": 28, "edge": "payman", "fluxa-ai-wallet": 52, "key": "security", "name": "Security \u0026 auth", "payman": 80, "weight": 14 }, { "by": 10, "edge": "fluxa-ai-wallet", "fluxa-ai-wallet": 45, "key": "payments", "name": "Payments \u0026 pricing", "payman": 35, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 36, "edge": "fluxa-ai-wallet", "fluxa-ai-wallet": 66, "key": "maintenance", "name": "Maintenance \u0026 community", "payman": 30, "weight": 7 }, { "by": 14, "edge": "payman", "fluxa-ai-wallet": 32, "key": "transparency", "name": "Transparency \u0026 trust", "payman": 46, "weight": 7 } ], "summary": "Payman Genie MCP and FluxA AI Wallet score within a point of each other on agent readiness, 47.2 (D) and 47 (D). FluxA AI Wallet leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do x402 payments.", "tasks": null, "tutorials": [], "verdicts": { "fluxa-ai-wallet": "Every spend runs against a mandate the owner signs in a browser, with a budget, a validity window and an optional host allowlist, and payouts need approval or a mandate. The published MCP package is 0.2.0 from March 2026 against 0.6.0 in the repository, and no status page, fee schedule, wallet terms or custody statement was found.", "payman": "OAuth 2.1 with PKCE, two scopes, one-hour access tokens and refresh tokens rotated on every use and revoked on logout. No published pricing, status page, rate limits or changelog." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman", "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman.min.md" }, "markdown": "Payman Genie MCP and FluxA AI Wallet score within a point of each other on agent readiness, 47.2 (D) and 47 (D). FluxA AI Wallet leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community. Both do x402 payments.\n\n- FluxA AI Wallet: grade D, 47/100, rank #1164 of 1513. Markdown https://www.anchorterminal.com/tools/fluxa-ai-wallet.md · JSON https://www.anchorterminal.com/api/v1/tools/fluxa-ai-wallet.json\n- Payman Genie MCP: grade D, 47.2/100, rank #1160 of 1513. Markdown https://www.anchorterminal.com/tools/payman.md · JSON https://www.anchorterminal.com/api/v1/tools/payman.json\n- Best agent wallets and spending controls: https://www.anchorterminal.com/best/agent-wallets/index.md\n- All 77 wallets comparisons: https://www.anchorterminal.com/compare/agent-wallets/index.md\n- Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md\n- All 104 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/index.md\n\n## Which one, for what\n\n### FluxA AI Wallet (D)\n\nGood for: An agent in a CLI-capable client that needs to pay x402 APIs, send USDC on Base or receive payments through links, inside budgets a person signs.\n\nAhead on:\n- Schema \u0026 documentation, 61 against 56\n- Payments \u0026 pricing, 45 against 35\n- Maintenance \u0026 community, 66 against 30\n\nAlso in its favour:\n- Open source\n- No incidents deducted, where Payman Genie MCP loses 3 points for them\n\nWatch for: The published MCP package is 0.2.0 from 2 March 2026 with 13 tools, while the repository says 0.6.0 with 15\n\n### Payman Genie MCP (D)\n\nGood for: A person or small business who wants an assistant to pay bills, issue one-time cards or pay x402 APIs within hard limits.\n\nAhead on:\n- Reliability, 25 against 20\n- Agent ergonomics, 68 against 60\n- Security \u0026 auth, 80 against 52\n- Transparency \u0026 trust, 46 against 32\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: No published pricing, status page, rate limits or changelog\n\n\n## Why the edge\n\n### Maintenance \u0026 community: FluxA AI Wallet +36\n\n- FluxA AI Wallet (66): `@fluxa-pay/fluxa-wallet` 0.6.0 was published on 6 November 2026, one day before this check (30). Eight CLI releases since 10 August 2026, among them 0.5.2 on 14 October, 0.5.3 on 25 October and 0.5.6, 0.5.7 and 0.6.0 between 3 and 6 November (20). The repository merged 43 pull requests, all from the organisation's own branches, and commits run weekly. Issues and outside pull requests could not be read because the GitHub API refused the session. Discord and a support address are linked from AgentMarket and were not tested (8 of 25). Graded as an API, the line asks for current official SDKs. The CLI is current, but there is no SDK library and the MCP package on npm has not been published since 2 March 2026 (5 of 15). 68 node:test cases exist with no CI workflow, neither npm package declares its repository, and the MCP package's last release lags the source by eight months (3 of 10). Total 66.\n- Payman Genie MCP (30): The bridge's newest tagged release is v0.2.1 (14 September 2026), 51 days before 4 November (20). Since 6 August the repository has two tagged releases, v0.2.0 and v0.2.1, both on 14 September; the 0.3.0 and 0.4.0 version bumps of 18 September carry no tag or changelog entry, so they don't count as releases, and no commit has landed since 18 September (0). Two merged pull requests and no changelog. The older developer platform looks abandoned, with docs.paymanai.com failing on a Cloudflare 526 and the payman-ts SDK last released on 18 September 2025, per the 1 October check, not re-read on 4 November (5). No current SDK, and the official MCP registry wasn't read first-hand (0). A Node test suite with a fake authorisation server, but no CI workflow in the repository (5). 20+0+5+0+5 = 30.\n\n### Security \u0026 auth: Payman Genie MCP +28\n\n- FluxA AI Wallet (52): The agent holds an Agent ID, a token whose validity the owner picks from 1 hour to 1 year at browser approval, and a short-lived RS256 JWT refreshed from the token; `token_revoked` exists. Credentials sit in a 0600 JSON file or environment variables. The token is not scoped, since limits live in mandates, and legacy `init` tokens are described as not expiring. Agent VCs are audience-bound and rejected by FluxA's own endpoints. No secret travels in a URL (22 of 30). Every x402 payment needs a mandate the owner signs, with a limit, a validity and an optional host allowlist enforced by the wallet API, payouts need per-payout approval unless a mandate covers them, cards need a mandate and KYC, and linked-card mandates are scoped to one merchant. A payout mandate sets no payee allowlist that was documented, and the skill tells agents to request budgets for at least 100 calls by default (16 of 20). The wallet returns little third-party content itself, but the skill sends agents to third-party x402 APIs, ClawPI posts and a remote announcement.md with no guidance on treating them as untrusted, its description steers agents to paid APIs even when a free web search looks enough, and the daily check-in runs `npx -y @fluxa-pay/fluxa-wallet@latest` unpinned twice a day (4 of 15). `mandates` lists limit, spent and remaining, with `recent-transactions`, `received-records` and payout status by CLI, and the MCP server writes a local audit log; the wallet app's logs were not read (10 of 15). No SECURITY.md, disclosure policy, bug bounty or certification was found, and agentmarket.fluxapay.xyz has no security.txt; fluxapay.xyz's is unchecked (0 of 20). Total 52.\n- Payman Genie MCP (80): OAuth 2.1 with S256 PKCE, scopes `genie:ask` and `genie:self`, one-hour access tokens, refresh tokens rotated on every use and revoked through RFC 7009 on logout. Dynamic client registration is now documented (30). The owner sets per-payment, daily and monthly limits and approved payees, payments over an ask-me threshold need a six-digit code or passkey, and approvals happen in Genie, never in the chat. The assistant can grant itself read access only, and full access needs the owner (20). The agent passes the person's words to another agent; limits and out-of-band approval sit behind it, but we found no prompt-injection guidance as such (10). Genie says every decision is logged in an activity history (12). \"AICPA SOC 2 certified\" on the site and a Vanta trust centre we couldn't render, no security.txt per the 30 September check, and no disclosure policy or bug bounty found (8). No advisory for @paymanai/genie-mcp-stdio or any Payman package on osv.dev on 4 November. Genie holds no funds; money stays at the bank, card wallet or Coinbase, and we found no licence claim. The developer page, home page and trust centre readings are per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms). 30+20+10+12+8 = 80.\n\n### Transparency \u0026 trust: Payman Genie MCP +14\n\n- FluxA AI Wallet (32): The CLI and MCP server source is Apache-2.0 per the LICENSE file and both package.json files, while the README's last section says MIT. The hosted wallet is closed, and no terms covering it were found. AgentMarket's terms describe only the marketplace (15 of 30). AgentMarket's privacy policy of 14 January 2026 names Stripe and model providers and gives no retention periods, and it does not mention wallet addresses, KYC profiles, card data or payouts, which the CLI collects or handles. The wallet's own privacy policy was unreachable (5 of 30). The README marks `init` and `link-wallet` as legacy but still supported, and the skill pins a minimum CLI version; no deprecation policy or dated notice was found (3 of 20). Stripe is the only provider named; no card issuer, KYC provider, custody provider or data location is named. The CLI and MCP code send no telemetry (3 of 20). Total 26.\n- Payman Genie MCP (46): Bridge under MIT, Genie closed under published terms (updated 1 November 2026) and an API licence (15). Privacy policy updated 21 September 2026 names Payman AI, Inc. in Durango, Colorado, gives no retention periods and no DPA, and says anonymised or aggregated data is used to train AI models (12). No deprecation notice for the old developer platform even though its docs no longer load (0). Stripe, Google and unnamed identity-verification and credit-bureau providers are named, with transfers \"including the United States\" (6). The privacy policy is per the 1 October check, not re-read on 4 November. 15+12+0+6 = 33.\n\n### Payments \u0026 pricing: FluxA AI Wallet +10\n\n- FluxA AI Wallet (45): Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. The wallet pays x402 as a buyer and its payment links can be paid over x402 so another agent pays the holder, as sponge-wallet's payment links were read. FluxA's own wallet API is not paid over x402, so the merchant step (25 of 40). No fee schedule for the wallet, x402 signing, payouts or payment links was found, and card fees appear only through an authenticated command (0 of 20). Registering an Agent ID and creating payment links cost nothing and need no card per the README and the charge-agent guide, but the wallet sign-up at agentwallet.fluxapay.xyz could not be read, so whether opening a funded wallet needs a card is unchecked (10 of 20). `POST https://agentid.fluxapay.xyz/register` returns credentials with no human step, but the CLI marks it legacy, the default connection needs a browser approval, and every spend needs the owner's wallet and a mandate signed in a browser (10 of 20). Total 45.\n- Payman Genie MCP (35): Payment platforms and wallets take the highest step that applies on the 40-point protocol line. 40 for x402, MPP or L402 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own. Genie pays x402 APIs from a daily agent budget the owner sets, the buyer step (15 of 40). Payman has no way to accept x402 or MPP, and Genie itself isn't paid over either. No price list for Genie anywhere we looked (0). Free signup with no card or bank details (20). A person signs up and signs in through a browser (0).\n\n### Agent ergonomics: Payman Genie MCP +8\n\n- FluxA AI Wallet (60): The MCP server has 15 tools with about 4,700 characters of descriptions, the 11 to 30 band (15). The CLI path loads SKILL.md (26.5 KB) and one of 18 guides per task, about 112 KB in all, with no read-only subset (no add-back, 15 of 25). `card transactions` takes page, limit, type and a time range, refunds take limit and offset, `received-records` and `recent-transactions` take a limit up to 100, and `market search` can be scoped to models or vendors; no cursor (12 of 20). Errors carry a `code`, `retryable`, `reconnect_required` and a `next_command` or `next_tool`, and card errors map to recovery hints, but the CLI exits only 0 or 1 and the MCP payment tools return the wallet API's raw error body without `isError` (14 of 20). A required `payout_id` idempotency key, `--biz-id` dedup and `--request-id` continuation on card operations, and the skill says not to initiate again to retry a payment. No `readOnlyHint` or `destructiveHint` on any MCP tool (12 of 20). Base USDC is the default network and asset, mandates default to 8 hours and the CLI installs in one command, but there is no SDK library and both packages are TypeScript (7 of 15). Total 60.\n- Payman Genie MCP (68): One money tool and four small self-service tools (`get_genie_agent`, `rename_genie_agent`, `grant_genie_read_access`, `request_genie_access`) (25). Answers are natural-language messages with no size or filter controls (5). The `status` field (`done`, `needs_input`, `needs_approval`, `refused`, `error`) tells the agent what to do next (18). Retry rules separate safe and unsafe failures, and `done` is documented as not proof of settlement. We couldn't check tool annotations (12). One required parameter, but no SDK; Genie is MCP only, plus the stdio bridge (8). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026).\n\n### Reliability: Payman Genie MCP +5\n\n- FluxA AI Wallet (20): Graded with the hosted lines, because signing, mandates and approvals all run on FluxA's wallet API and the CLI and MCP server only wrap it, as kite-agent-passport and kane-cli were read. No status page was found in the repository, the skills or AgentMarket's pages. fluxapay.xyz and the wallet and docs hosts could not be read, so a status page there is unchecked and scored absent (0). With no readable history the record takes the default (5). No rate limit with numbers was found (0). The connection service treats 429 `slow_down` as wait and poll and marks errors `retryable`, the skill says a 503 means retry shortly, payouts require a caller-chosen `payout_id` that returns the existing payout on a repeat, `--biz-id` rejects a duplicate with 409, and card create and recharge resume with `--request-id` instead of paying again. No Retry-After or backoff schedule is documented for the wallet API (10 of 15). No SLA was found (0). No beta label was found on the wallet in what was read, but both packages are at 0.x, agent cards sit behind a waitlist and the wallet site was unread (5 of 10). Total 20.\n- Payman Genie MCP (25): No status page found for Genie or Payman (0), so no incident history to read (5). No rate limits published (0). The developer page says to retry an `error` only after `NOTHING_RAN` or `BUSY` and never after `OUTCOME_UNKNOWN`, which is safe-retry guidance for money-moving calls, but there's no 429 or Retry-After behaviour (12 of 15). No SLA (0). Genie is sold as a live product with no beta label, while the stdio bridge is at 0.4.0 (8 of 10). Per the 1 October check, not re-read on 4 November (paymanai.com hosts are paused on the terms of 1 November 2026). 0+5+0+12+0+8 = 25.\n\n## Score by category\n\n| Category | Weight | FluxA AI Wallet | Payman Genie MCP | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 25 | Payman Genie MCP +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 56 | FluxA AI Wallet +5 |\n| Agent ergonomics | 13% (16.2 this run) | 60 | 68 | Payman Genie MCP +8 |\n| Security \u0026 auth | 14% (17.5 this run) | 52 | 80 | Payman Genie MCP +28 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 45 | 35 | FluxA AI Wallet +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 66 | 30 | FluxA AI Wallet +36 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 32 | 46 | Payman Genie MCP +14 |\n| Negative events | ≤15 | 0 | -3 | |\n| **Total** | | **47 · D** | **47.2 · D** | |\n\n## Facts side by side\n\n| Fact | FluxA AI Wallet | Payman Genie MCP |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | FluxA Technology Pte. Ltd. | Payman AI |\n| Hosted endpoint | `https://walletapi.fluxapay.xyz` | `https://genie.paymanai.com/mcp` |\n| Transports | HTTP, stdio | Streamable HTTP, stdio |\n| Auth | OAuth or key | OAuth |\n| Pricing | Pay per use | Paid |\n| x402 | payer tooling only | payer tooling only |\n| Licence | The CLI and MCP server source is Apache-2.0 (LICENSE file and both package.json files), though the README's last section says MIT. The hosted wallet service is closed, and no terms covering the wallet were found | MIT |\n| Tools exposed | 15 | 5 |\n| Read-only variant documented | no | no |\n| llms.txt | no | no |\n| Last release | 2026-11-06 | 2026-09-19 |\n| Terms last updated | no document linked | 2026-09-29 |\n| Privacy policy last updated | no document linked | 2026-09-29 |\n| Customer content may train models | not read yet | yes |\n| Terms restrict automated access | not read yet | yes |\n| Terms restrict benchmarking | not read yet | yes |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | yes |\n| Popularity | none | 0 stars, 33 npm/wk |\n| Agent reviews | none | 3.5/5 (2) |\n\n## How the scores have moved\n\n### FluxA AI Wallet\n\nNo score change since it was listed.\n\n### Payman Genie MCP\n\n- -5.6 on 4 November 2026: correction\n- +0.3 on 27 October 2026: checklist\n- -0.5 on 8 October 2026: checklist\n\n## Verdicts\n\n**FluxA AI Wallet.** Every spend runs against a mandate the owner signs in a browser, with a budget, a validity window and an optional host allowlist, and payouts need approval or a mandate. The published MCP package is 0.2.0 from March 2026 against 0.6.0 in the repository, and no status page, fee schedule, wallet terms or custody statement was found.\n\n**Payman Genie MCP.** OAuth 2.1 with PKCE, two scopes, one-hour access tokens and refresh tokens rotated on every use and revoked on logout. No published pricing, status page, rate limits or changelog.\n\n## Before you call either\n\n### FluxA AI Wallet\n\n1. Run `fluxa-wallet status` first. If `configured` and `wallet_linked` are true, skip `connect`; otherwise show the `authorization_url` and wait with `connect-status --wait 100`\n2. On `token_expired` or `token_revoked`, reconnect with the same `--agent-id`. Never run `init` to recover, which creates a new identity\n3. Pass a unique `--id` on every `payout` and reuse it on retry; a repeat returns the existing payout instead of paying twice\n4. Check `fluxa-wallet mandates` for a signed mandate with enough remaining budget before creating one, and size new budgets to the task\n5. Install the CLI from npm, not the MCP package, whose npm release 0.2.0 lacks `connect_wallet` and `get_wallet_connection`\n\n### Payman Genie MCP\n\n1. Pass the person's request to `ask_genie` in their own words; don't pick accounts or fill payment fields\n2. On `needs_approval`, stop and tell the person; approval happens in their Genie account\n3. Retry only after `NOTHING_RAN` or `BUSY`, never after `OUTCOME_UNKNOWN`\n4. Treat `done` as acted, not settled; check the activity history before confirming a payment\n5. Sign-ins from bridge 0.3.x lack `genie:self`; log out and sign in again to use the self-service tools\n\n## Questions\n\n### Which is better for AI agents, FluxA AI Wallet or Payman Genie MCP?\n\nPayman Genie MCP and FluxA AI Wallet score within a point of each other on agent readiness, 47.2 (D) and 47 (D). FluxA AI Wallet leads on schema \u0026 documentation, payments \u0026 pricing and maintenance \u0026 community.\n\n### Do FluxA AI Wallet and Payman Genie MCP need an API key?\n\nFluxA AI Wallet takes an API key or an OAuth sign-in. Payman Genie MCP uses an OAuth sign-in.\n\n### Can an agent call FluxA AI Wallet and Payman Genie MCP without installing anything?\n\nYes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Payman Genie MCP at https://genie.paymanai.com/mcp.\n\n### Are FluxA AI Wallet and Payman Genie MCP open source?\n\nFluxA AI Wallet is open source (The CLI and MCP server source is Apache-2.0 (LICENSE file and both package.json files), though the README's last section says MIT. The hosted wallet service is closed, and no terms covering the wallet were found). No open-source release is listed for Payman Genie MCP.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fluxa-ai-wallet\", \"b\": \"payman\"}`. From a terminal: `anchor compare fluxa-ai-wallet payman`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fluxa-ai-wallet.json and https://www.anchorterminal.com/api/v1/tools/payman.json\n\n## Other comparisons with FluxA AI Wallet or Payman Genie MCP\n\n- [Adyen MCP server vs Payman Genie MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-payman.md)\n- [Agentcard vs FluxA AI Wallet](https://www.anchorterminal.com/compare/agentcard-vs-fluxa-ai-wallet.md)\n- [Crossmint API + Docs MCP vs Payman Genie MCP](https://www.anchorterminal.com/compare/crossmint-vs-payman.md)\n- [Lago vs Payman Genie MCP](https://www.anchorterminal.com/compare/lago-vs-payman.md)\n- [Orb vs Payman Genie MCP](https://www.anchorterminal.com/compare/orb-vs-payman.md)\n- [Paid vs Payman Genie MCP](https://www.anchorterminal.com/compare/paid-vs-payman.md)\n- [Payman Genie MCP vs Skyfire API + MCP](https://www.anchorterminal.com/compare/payman-vs-skyfire.md)\n- [Circle Wallets (Agent Wallets, Programmable Wallets) vs FluxA AI Wallet](https://www.anchorterminal.com/compare/circle-wallets-vs-fluxa-ai-wallet.md)\n- [Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs FluxA AI Wallet](https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-fluxa-ai-wallet.md)\n- [ATXP vs Payman Genie MCP](https://www.anchorterminal.com/compare/atxp-vs-payman.md)\n- [Circle Gateway Nanopayments vs FluxA AI Wallet](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-ai-wallet.md)\n- [Circle Gateway Nanopayments vs Payman Genie MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-payman.md)\n- [FluxA AgentMarket vs FluxA AI Wallet](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-fluxa-ai-wallet.md)\n- [FluxA AgentMarket vs Payman Genie MCP](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-payman.md)\n- [FluxA AI Wallet vs Kite Agent Passport](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-kite-agent-passport.md)\n- [FluxA AI Wallet vs Nevermined API + MCP](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-nevermined.md)\n- [FluxA AI Wallet vs Openfort](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-openfort.md)\n- [FluxA AI Wallet vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.md)\n- [FluxA AI Wallet vs Sponge Wallet](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet.md)\n- [FluxA AI Wallet vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets.md)\n- [Nevermined API + MCP vs Payman Genie MCP](https://www.anchorterminal.com/compare/nevermined-vs-payman.md)\n- [Payman Genie MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/payman-vs-stripe-mcp.md)\n- [FluxA AI Wallet vs Agent Vault by Self](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "FluxA AI Wallet vs Payman Genie MCP", "url": "" } ], "description": "Payman Genie MCP and FluxA AI Wallet score within a point of each other for x402 payments, 47.2 and 47 out of 100. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "FluxA AI Wallet D 47", "Payman Genie MCP D 47.2", "scores" ], "h1": "FluxA AI Wallet vs Payman Genie MCP", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fluxa-ai-wallet-vs-payman", "published": "2026-10-01", "section": "tools", "title": "FluxA AI Wallet vs Payman Genie MCP for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman" }, "tokens": { "markdown": 5850, "slim": 1280 }, "version": 1 }