{ "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": "Privy Wallets (server wallets, agent wallets, policy engine) scores 72.3 (BB) on agent readiness against FluxA AI Wallet's 47 (D), and leads in every scored category.", "b": { "slug": "privy", "name": "Privy Wallets (server wallets, agent wallets, policy engine)", "vendor": "Privy (Stripe)", "vendorUrl": "https://www.privy.io", "kind": "http-api", "category": "agent-wallets", "summary": "Privy's wallet API for apps and AI agents, with server wallets and a policy engine that limits what each wallet can sign. Owned by Stripe since June 2025.", "url": "https://www.anchorterminal.com/tools/privy", "markdownUrl": "https://www.anchorterminal.com/tools/privy.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/privy.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/privy.json", "dns": "privy.grade.anchorterminal.com", "transports": [ "http" ], "remoteUrl": "https://api.privy.io/v1", "packages": [ { "registry": "npm", "name": "@privy-io/node" }, { "registry": "npm", "name": "@privy-io/agent-wallet-cli" }, { "registry": "pypi", "name": "privy-client" } ], "auth": "mixed", "authNotes": "REST API uses Basic auth with app ID and app secret plus a privy-app-id header. Wallets owned by an authorisation key (or a key quorum) also need a signature from that key on each request. The Agent CLI uses a device authorisation flow approved in a browser, then short-lived signing keys; sessions last up to 30 days.", "pricing": "freemium", "pricingNotes": "Developer plan free up to 499 monthly active users, with 50,000 signatures and $1M transaction volume a month included. Core $299 a month (500 to 2,499 MAU) and Scale $499 a month (2,500 to 9,999 MAU). Past 10,000 MAU or 50,000 signatures, a $2,000 base plus $0.05 per MAU and $0.01 per signature. Enterprise is custom, from $0.001 per signature, with premium SLAs (https://www.privy.io/pricing).", "priceSummary": "$299 / mo", "where": "hosted", "x402": { "level": "partial", "evidence": "Privy ships x402 and MPP payer clients (createX402Client in Node, useX402Fetch in React) that sign 402 payment authorisations with a Privy wallet and retry; x402 works with gas-sponsored wallets. React's wrapper takes a per-request maxValue cap, and the Node client has applied spend controls with a $1 default cap per payment since @privy-io/node 0.37.0 (26 October 2026). Privy's own API isn't paid via x402 (https://docs.privy.io/recipes/agent-integrations/x402.md; https://github.com/privy-io/node-sdk/blob/main/CHANGELOG.md).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 296371, "pypiWeekly": 12798, "asOf": "2026-09-30" }, "docsUrl": "https://docs.privy.io/wallets/overview/solutions/agent-wallets", "llmsTxt": "https://docs.privy.io/llms.txt", "openapi": "https://api.privy.io/v1/openapi.json", "capabilities": [ "wallet.onchain", "wallet.custody", "wallet.spend-limits", "payments.x402" ], "tags": [ "hosted", "freemium", "free-tier", "llms-txt", "openapi", "typescript", "python", "wallet", "stablecoin", "x402", "closed-source", "webhooks" ], "lastRelease": "2026-10-26", "graded": true, "anchor": { "graded": true, "score": 72.3, "grade": "BB", "agentReady": true, "rank": 132, "ranked": true, "rankOf": 1513, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 81, "maintenance": 80, "payments": 55, "reliability": 53, "schema": 83, "security": 85, "transparency": 72 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Default-deny policies with DENY precedence on recipients, values, contracts, calldata, typed data and time windows, enforced in AWS Nitro Enclaves. Database problems caused outages across API endpoints for 71 minutes on 18 September 2026, and rate limits aren't published as numbers.", "bestFor": "Builders who need fine-grained, enclave-enforced spending rules on programmatic wallets, or who want an agent to sign for a person's wallet with a revocable scoped signer.", "strengths": [ "Default-deny policies with DENY precedence on recipients, values, contracts, calldata, typed data and time windows, enforced in AWS Nitro Enclaves", "Agent-owned wallets or revocable scoped signers on a person's wallet, plus key quorums for m-of-n approval", "Idempotency keys on every state-changing wallet route, honoured for 24 hours", "SOC 2 Type I and II, audits by Cure53, Zellic and Doyensec, and a HackerOne bug bounty", "x402 and MPP payer clients; the Node x402 client caps each payment at $1 by default since 0.37.0 (26 October 2026)" ], "weaknesses": [ "Database problems caused outages across API endpoints for 71 minutes on 18 September 2026, one of 13 incidents since 3 August", "Rate limits aren't published as numbers", "Rolling caps are EVM only and update after signing, so parallel requests can exceed them", "The app secret can do anything in the app; the limits come from authorisation keys and policies", "No MCP server for wallet actions, and the Agent CLI needs a person to approve its login in a browser" ], "agentNotes": [ "Add a rule for every RPC method the agent needs; a wallet with a policy denies anything unlisted", "Pair a rolling cap with a lower per-transaction cap, since aggregations update only after signing", "Send an idempotency key on `/rpc`, `/transfer` and `/wallets` calls; reusing one with a changed body returns 400", "Set `maxValue` in React or `spendControls` in Node (0.37.0 or later) on the x402 client; the MPP guide shows no cap, so rely on wallet policies there", "Retry a `transaction_broadcast_failure`; don't retry a `policy_violation`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "BB", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 72.3 } ], "editorialScores": { "ergonomics": 81, "maintenance": 80, "payments": 55, "reliability": 53, "schema": 83, "security": 85, "transparency": 60 }, "provenanceScore": 84, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-11-01", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install -g @privy-io/agent-wallet-cli", "http": "curl https://api.privy.io/v1/wallets --user \"$PRIVY_APP_ID:$PRIVY_APP_SECRET\" -H \"privy-app-id: $PRIVY_APP_ID\"" }, "letme": { "capability": "https://letme.dev/wallet.onchain", "tool": "https://letme.dev/privy" }, "area": "payments", "unitPrices": [ { "item": "Core plan", "unit": "month", "usd": 299, "note": "500 to 2,499 MAU" }, { "item": "Scale plan", "unit": "month", "usd": 499, "note": "2,500 to 9,999 MAU" }, { "item": "Signature overage", "unit": "call", "usd": 0.01, "note": "per signature above 50,000 a month" } ], "provenance": { "legalEntity": "Horkos, LLC", "domain": "privy.io", "domainRegistered": "2018-10-07", "domainNote": "Privy trades as Horkos, LLC d/b/a Privy, a Stripe subsidiary since June 2025.", "endpointOnVendorDomain": true, "terms": "https://www.privy.io/developer-terms-of-service", "privacy": "https://www.privy.io/privacy-policy", "statusPage": "https://status.privy.io", "changelog": "https://docs.privy.io/changelogs/product-updates", "securityTxt": "none", "checked": "2026-09-30", "score": 84 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/privy.json", "live": { "slug": "privy", "probe": { "target": "https://api.privy.io/v1", "method": "get", "lastAt": "2026-11-08T14:48:06.715722247Z", "lastOk": true, "lastStatus": 404, "lastMs": 42, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 37, "p95ms24h": 121, "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" }, "vendorStatus": { "page": "https://status.privy.io", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T14:51:36.597416118Z" }, "versions": [ { "registry": "npm", "name": "@privy-io/agent-wallet-cli", "version": "0.3.11", "seenAt": "2026-11-08T01:30:30.03609154Z" }, { "registry": "npm", "name": "@privy-io/node", "version": "0.38.0", "seenAt": "2026-11-08T01:30:29.109132208Z" }, { "registry": "pypi", "name": "privy-client", "version": "0.7.0", "released": "2026-09-08", "seenAt": "2026-11-08T01:30:31.297328216Z" } ], "npmWeekly": 420097, "pypiWeekly": 23876, "securityTxt": { "url": "https://privy.io/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:53.267989909Z" }, "llmsTxt": { "url": "https://docs.privy.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:41.871307001Z" }, "domain": { "domain": "privy.io", "checkedAt": "2026-11-01T14:13:42.593459427Z" }, "pages": [ { "url": "https://docs.privy.io/changelogs/product-updates", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:36.997742057Z", "changedAt": "2026-10-29T05:05:27.907362965Z", "fingerprint": "118c12d51c7b" }, { "url": "https://www.privy.io/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:33:19.075529033Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3fafdab3dba6" }, { "url": "https://www.privy.io/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:33:21.219636719Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "3dc0c2d903e9" }, { "url": "https://www.privy.io/developer-terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:33:16.722381494Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "b057defa15d5" } ], "updatedAt": "2026-11-08T14:51:36.597416118Z" }, "streak": { "days": 31, "from": "2026-10-08", "sinceWatching": true, "best": 31 } }, "edges": [ { "by": 40, "category": "transparency", "leads": "privy", "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": "Closed service under developer terms; the Agent CLI is Apache-2.0 and the Shamir secret-sharing library is open source (18 of 30). The privacy policy, updated 20 May 2026, names Horkos, LLC d/b/a Privy with Stripe as parent, separates controller and service-provider roles, has a DPA with standard clauses and says Privy can never rebuild users' keys, which matches the architecture docs; it gives no retention periods (20 of 30). Weekly product updates, but no dated deprecation notices found (6 of 20). Subprocessors listed in a linked trust centre, and hosting stated as the United States (16 of 20)." }, "scores": { "a": 32, "b": 72 } }, { "by": 33, "category": "reliability", "leads": "privy", "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": "Status page at status.privy.io with components and an RSS history back to October 2025 (20). The 90 days from 3 August hold 13 incidents. Database problems caused outages across API endpoints for 71 minutes on 18 September, one major. The rest were partial or delays and read as minor, among them a portion of /api/v1/sessions calls failing for 78 minutes on 3 August, wallet actions and finality delayed for 1 hour 59 minutes on 18 September, an upstream outage that hit wallet transactions for 2 hours 11 minutes and delayed webhooks for 3 hours 40 minutes on 10 October, and elevated RPC failures, mostly in the EU, for 1 hour 12 minutes on 28 October (10 of 30). Rate limits are enforced per app with 429s, but no numbers are published (0). Idempotency keys on state-changing POSTs such as `/rpc`, `/transfer` and `/wallets`, honoured for 24 hours, and the error guide says when a retry is safe; no 429 or backoff guidance found, and the OpenAPI file documents no 429 response (10 of 15). The pricing page lists \"premium SLAs\" on Enterprise without publishing terms (5 of 10). The wallet API is generally available; the Agent CLI is 0.3.10 (8 of 10). 20+10+0+10+5+8 = 53." }, "scores": { "a": 20, "b": 53 } }, { "by": 33, "category": "security", "leads": "privy", "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": "The app secret on Basic auth can do anything in the app, but wallets owned by an authorisation key or a key quorum also need that key's signature on each request, delegated signers on user wallets can be revoked, and the Agent CLI uses a device flow with short-lived signing keys and sessions of up to 30 days with rotation (27 of 30). Policies deny by default, DENY beats ALLOW, and rules cover recipients, values, contracts, decoded calldata, typed data and time windows, enforced inside AWS Nitro Enclaves before signing; key quorums add m-of-n approval. React's x402 fetch wrapper takes a `maxValue` cap, and the Node x402 client gained spend controls with a $1 default cap per payment in 0.37.0 (26 October 2026); the MPP guide shows no cap. Rolling caps are EVM only and update after signing, per the 30 September check (19 of 20). We found no prompt-injection guidance for agents reading wallet or token data (8 of 15). Activity logs and webhooks (13 of 15). SOC 2 Type I and Type II, audits by Cure53, Zellic and Doyensec, a HackerOne bug bounty and a disclosure page at privy.io/vulnerability-disclosure; no security.txt (18 of 20)." }, "scores": { "a": 52, "b": 85 } }, { "by": 22, "category": "schema", "leads": "privy", "name": "Schema \u0026 documentation", "reasons": { "a": "No OpenAPI file or reference for the wallet API was found; the README shows sample requests for five endpoints. The MCP server's 15 tools in the 0.6.0 source carry typed Zod input schemas, and the CLI's flags are documented in prose in the skill files and `--help`. The MCP server is the secondary surface and its npm release is 0.2.0, so 12 of 25. The skill and its 18 Markdown guides are written for agents, and AgentMarket's llms.txt describes the wallet's payment role (10). `connect_wallet`, `init_agent_id` and `create_intent_mandate` say when to use them and when not to, and the skill has a when-to-use table per capability, while the payment-link and status tools have one-line descriptions (12 of 20). Zod enums for validity, runtime, hosting and currency, a regex on payout amounts and strict objects, but the x402 requirement fields are plain strings and `outputSchema` is a free-form record (10 of 15). The README has an example for every MCP tool, the skills give CLI examples and output, and error codes are tabled for mandates, payouts, cards and connections (12 of 15). Semver on npm with 25 CLI versions and a version line in the skill, two git tags and no changelog (5 of 15). Total 61.", "b": "A public OpenAPI 3.1 document at api.privy.io/v1/openapi.json, 178 paths and 231 operations on 1 November, though its `info.version` is 0.0.1 (25). llms.txt with 400+ links and Markdown twins (10). The docs explain what each wallet action and policy field is for; we didn't read every reference page (14 of 20). Policy conditions are typed by field source and operator, with a `chain_type` on every policy (13 of 15). Ten named API error codes, each with troubleshooting steps, and examples in the docs, but no table of HTTP statuses (11 of 15). `/v1` paths and weekly product updates, but the OpenAPI version has never moved off 0.0.1 (10 of 15)." }, "scores": { "a": 61, "b": 83 } }, { "by": 21, "category": "ergonomics", "leads": "privy", "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": "No product MCP server (the docs MCP at docs.privy.io/mcp only searches documentation), so an agent works through the API, SDKs or the Agent CLI, and response sizing is ordinary REST (15 of 25). The OpenAPI file gives `cursor` and `limit` on the main lists (`/v1/wallets`, `/v1/users`, `/v1/policies`), filters such as `chain_type`, `address`, `user_id` and `include_archived` on wallets, and `include` flags elsewhere, but list routes such as `/v1/transactions` and `/v1/actions` take no paging parameters (18 of 20). Errors such as `policy_violation`, `insufficient_funds` and `transaction_broadcast_failure` come with recovery steps, and the guide says a failed broadcast is safe to retry (16 of 20). Idempotency keys on every state-changing wallet route, 24-hour window, 400 on a changed body (20). SDKs for Node (0.37.0), Python, Go, Rust, Ruby, Java, React and Flutter plus the Agent CLI, but requests on key-owned wallets also need an authorisation signature (12 of 15). 15+18+16+20+12 = 81." }, "scores": { "a": 60, "b": 81 } }, { "by": 14, "category": "maintenance", "leads": "privy", "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": "@privy-io/node 0.37.0 on 26 October 2026, and a weekly product update on 16 October (30). Node SDK 0.29.0 to 0.37.0, nine releases between 17 August and 26 October, and weekly product updates on 7 and 14 August, 18 and 25 September and 2, 9 and 16 October (20). Weekly product updates and monthly rollups through September 2026; we didn't test a support channel (10 of 15). Current official SDKs in Node, Python, Go, Rust, Ruby and Java, plus React and Flutter (15). The Agent CLI is pre-1.0 (0.3.10). The Node SDK's CI workflows are in its public repository, but we couldn't see run results (5 of 10). 30+20+10+15+5 = 80. The 1 October note put 0.35.0 on 28 September; the changelog and tag date it 21 September." }, "scores": { "a": 66, "b": 80 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "FluxA Technology Pte. Ltd.", "b": "Privy (Stripe)", "name": "Vendor" }, { "a": "https://walletapi.fluxapay.xyz", "b": "https://api.privy.io/v1", "name": "Hosted endpoint" }, { "a": "HTTP, stdio", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth or key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "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": "none", "name": "Licence" }, { "a": "15", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "2026-11-06", "b": "2026-10-26", "name": "Last release" }, { "a": "no document linked", "b": "2025-12-16", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "296k npm/wk, 13k PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "Privy Wallets (server wallets, agent wallets, policy engine) scores 72.3 (BB) on agent readiness against FluxA AI Wallet's 47 (D), and leads in every scored category.", "question": "Which is better for AI agents, FluxA AI Wallet or Privy Wallets (server wallets, agent wallets, policy engine)?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do FluxA AI Wallet and Privy Wallets (server wallets, agent wallets, policy engine) need an API key?" }, { "answer": "Yes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Privy Wallets (server wallets, agent wallets, policy engine) at https://api.privy.io/v1.", "question": "Can an agent call FluxA AI Wallet and Privy Wallets (server wallets, agent wallets, policy engine) 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 Privy Wallets (server wallets, agent wallets, policy engine).", "question": "Are FluxA AI Wallet and Privy Wallets (server wallets, agent wallets, policy engine) open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "Runs on your own machine", "Open source" ], "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, 53 against 20", "Schema \u0026 documentation, 83 against 61", "Agent ergonomics, 81 against 60", "Security \u0026 auth, 85 against 52", "Payments \u0026 pricing, 55 against 45", "Maintenance \u0026 community, 80 against 66", "Transparency \u0026 trust, 72 against 32" ], "also": [ "Agent-ready, a grade of BB or better" ], "goodFor": "Builders who need fine-grained, enclave-enforced spending rules on programmatic wallets, or who want an agent to sign for a person's wallet with a revocable scoped signer.", "slug": "privy", "watchFor": "Database problems caused outages across API endpoints for 71 minutes on 18 September 2026, one of 13 incidents since 3 August" } ], "history": { "fluxa-ai-wallet": null, "privy": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-01", "delta": 2.3, "from": 70, "fromGrade": "BB", "to": 72.3, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 69.9, "fromGrade": "B", "to": 70, "toGrade": "BB" }, { "causes": [ "method" ], "date": "2026-10-08", "delta": -0.2, "from": 70.1, "fromGrade": "BB", "to": 69.9, "toGrade": "B" } ] }, "job": { "capability": "payments.x402", "name": "x402 payments" }, "others": [ { "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/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/circle-wallets-vs-privy.json", "title": "Circle Wallets (Agent Wallets, Programmable Wallets) vs Privy Wallets (server wallets, agent wallets, policy engine)", "url": "https://www.anchorterminal.com/compare/circle-wallets-vs-privy" }, { "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/coinbase-cdp-agentkit-vs-privy.json", "title": "Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Privy Wallets (server wallets, agent wallets, policy engine)", "url": "https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-privy" }, { "json": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-privy.json", "title": "Kite Agent Passport vs Privy Wallets (server wallets, agent wallets, policy engine)", "url": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-privy" }, { "json": "https://www.anchorterminal.com/compare/openfort-vs-privy.json", "title": "Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)", "url": "https://www.anchorterminal.com/compare/openfort-vs-privy" }, { "json": "https://www.anchorterminal.com/compare/privy-vs-sponge-wallet.json", "title": "Privy Wallets (server wallets, agent wallets, policy engine) vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/privy-vs-sponge-wallet" }, { "json": "https://www.anchorterminal.com/compare/privy-vs-turnkey-agentic-wallets.json", "title": "Privy Wallets (server wallets, agent wallets, policy engine) vs Turnkey Agentic Wallets", "url": "https://www.anchorterminal.com/compare/privy-vs-turnkey-agentic-wallets" }, { "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/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-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-payman.json", "title": "FluxA AI Wallet vs Payman Genie MCP", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman" }, { "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/agentcard-vs-privy.json", "title": "Agentcard vs Privy Wallets (server wallets, agent wallets, policy engine)", "url": "https://www.anchorterminal.com/compare/agentcard-vs-privy" }, { "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" }, { "json": "https://www.anchorterminal.com/compare/privy-vs-self-agent-vault.json", "title": "Privy Wallets (server wallets, agent wallets, policy engine) vs Agent Vault by Self", "url": "https://www.anchorterminal.com/compare/privy-vs-self-agent-vault" } ], "panel": null, "scores": [ { "by": 33, "edge": "privy", "fluxa-ai-wallet": 20, "key": "reliability", "name": "Reliability", "privy": 53, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 22, "edge": "privy", "fluxa-ai-wallet": 61, "key": "schema", "name": "Schema \u0026 documentation", "privy": 83, "weight": 13 }, { "by": 21, "edge": "privy", "fluxa-ai-wallet": 60, "key": "ergonomics", "name": "Agent ergonomics", "privy": 81, "weight": 13 }, { "by": 33, "edge": "privy", "fluxa-ai-wallet": 52, "key": "security", "name": "Security \u0026 auth", "privy": 85, "weight": 14 }, { "by": 10, "edge": "privy", "fluxa-ai-wallet": 45, "key": "payments", "name": "Payments \u0026 pricing", "privy": 55, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 14, "edge": "privy", "fluxa-ai-wallet": 66, "key": "maintenance", "name": "Maintenance \u0026 community", "privy": 80, "weight": 7 }, { "by": 40, "edge": "privy", "fluxa-ai-wallet": 32, "key": "transparency", "name": "Transparency \u0026 trust", "privy": 72, "weight": 7 } ], "summary": "Privy Wallets (server wallets, agent wallets, policy engine) scores 72.3 (BB) on agent readiness against FluxA AI Wallet's 47 (D), and leads in every scored category. Both do x402 payments.", "tasks": null, "tutorials": [ { "title": "Find an agent wallet by external ID with Privy", "tool": "privy", "url": "https://www.anchorterminal.com/tutorials/privy/" } ], "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.", "privy": "Default-deny policies with DENY precedence on recipients, values, contracts, calldata, typed data and time windows, enforced in AWS Nitro Enclaves. Database problems caused outages across API endpoints for 71 minutes on 18 September 2026, and rate limits aren't published as numbers." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy", "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.min.md" }, "markdown": "Privy Wallets (server wallets, agent wallets, policy engine) scores 72.3 (BB) on agent readiness against FluxA AI Wallet's 47 (D), and leads in every scored category. 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- Privy Wallets (server wallets, agent wallets, policy engine): grade BB, 72.3/100, rank #132 of 1513. Markdown https://www.anchorterminal.com/tools/privy.md · JSON https://www.anchorterminal.com/api/v1/tools/privy.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\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\nAlso in its favour:\n- Runs on your own machine\n- Open source\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### Privy Wallets (server wallets, agent wallets, policy engine) (BB)\n\nGood for: Builders who need fine-grained, enclave-enforced spending rules on programmatic wallets, or who want an agent to sign for a person's wallet with a revocable scoped signer.\n\nAhead on:\n- Reliability, 53 against 20\n- Schema \u0026 documentation, 83 against 61\n- Agent ergonomics, 81 against 60\n- Security \u0026 auth, 85 against 52\n- Payments \u0026 pricing, 55 against 45\n- Maintenance \u0026 community, 80 against 66\n- Transparency \u0026 trust, 72 against 32\n\nAlso in its favour:\n- Agent-ready, a grade of BB or better\n\nWatch for: Database problems caused outages across API endpoints for 71 minutes on 18 September 2026, one of 13 incidents since 3 August\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Privy Wallets (server wallets, agent wallets, policy engine) +40\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- Privy Wallets (server wallets, agent wallets, policy engine) (72): Closed service under developer terms; the Agent CLI is Apache-2.0 and the Shamir secret-sharing library is open source (18 of 30). The privacy policy, updated 20 May 2026, names Horkos, LLC d/b/a Privy with Stripe as parent, separates controller and service-provider roles, has a DPA with standard clauses and says Privy can never rebuild users' keys, which matches the architecture docs; it gives no retention periods (20 of 30). Weekly product updates, but no dated deprecation notices found (6 of 20). Subprocessors listed in a linked trust centre, and hosting stated as the United States (16 of 20).\n\n### Reliability: Privy Wallets (server wallets, agent wallets, policy engine) +33\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- Privy Wallets (server wallets, agent wallets, policy engine) (53): Status page at status.privy.io with components and an RSS history back to October 2025 (20). The 90 days from 3 August hold 13 incidents. Database problems caused outages across API endpoints for 71 minutes on 18 September, one major. The rest were partial or delays and read as minor, among them a portion of /api/v1/sessions calls failing for 78 minutes on 3 August, wallet actions and finality delayed for 1 hour 59 minutes on 18 September, an upstream outage that hit wallet transactions for 2 hours 11 minutes and delayed webhooks for 3 hours 40 minutes on 10 October, and elevated RPC failures, mostly in the EU, for 1 hour 12 minutes on 28 October (10 of 30). Rate limits are enforced per app with 429s, but no numbers are published (0). Idempotency keys on state-changing POSTs such as `/rpc`, `/transfer` and `/wallets`, honoured for 24 hours, and the error guide says when a retry is safe; no 429 or backoff guidance found, and the OpenAPI file documents no 429 response (10 of 15). The pricing page lists \"premium SLAs\" on Enterprise without publishing terms (5 of 10). The wallet API is generally available; the Agent CLI is 0.3.10 (8 of 10). 20+10+0+10+5+8 = 53.\n\n### Security \u0026 auth: Privy Wallets (server wallets, agent wallets, policy engine) +33\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- Privy Wallets (server wallets, agent wallets, policy engine) (85): The app secret on Basic auth can do anything in the app, but wallets owned by an authorisation key or a key quorum also need that key's signature on each request, delegated signers on user wallets can be revoked, and the Agent CLI uses a device flow with short-lived signing keys and sessions of up to 30 days with rotation (27 of 30). Policies deny by default, DENY beats ALLOW, and rules cover recipients, values, contracts, decoded calldata, typed data and time windows, enforced inside AWS Nitro Enclaves before signing; key quorums add m-of-n approval. React's x402 fetch wrapper takes a `maxValue` cap, and the Node x402 client gained spend controls with a $1 default cap per payment in 0.37.0 (26 October 2026); the MPP guide shows no cap. Rolling caps are EVM only and update after signing, per the 30 September check (19 of 20). We found no prompt-injection guidance for agents reading wallet or token data (8 of 15). Activity logs and webhooks (13 of 15). SOC 2 Type I and Type II, audits by Cure53, Zellic and Doyensec, a HackerOne bug bounty and a disclosure page at privy.io/vulnerability-disclosure; no security.txt (18 of 20).\n\n### Schema \u0026 documentation: Privy Wallets (server wallets, agent wallets, policy engine) +22\n\n- FluxA AI Wallet (61): No OpenAPI file or reference for the wallet API was found; the README shows sample requests for five endpoints. The MCP server's 15 tools in the 0.6.0 source carry typed Zod input schemas, and the CLI's flags are documented in prose in the skill files and `--help`. The MCP server is the secondary surface and its npm release is 0.2.0, so 12 of 25. The skill and its 18 Markdown guides are written for agents, and AgentMarket's llms.txt describes the wallet's payment role (10). `connect_wallet`, `init_agent_id` and `create_intent_mandate` say when to use them and when not to, and the skill has a when-to-use table per capability, while the payment-link and status tools have one-line descriptions (12 of 20). Zod enums for validity, runtime, hosting and currency, a regex on payout amounts and strict objects, but the x402 requirement fields are plain strings and `outputSchema` is a free-form record (10 of 15). The README has an example for every MCP tool, the skills give CLI examples and output, and error codes are tabled for mandates, payouts, cards and connections (12 of 15). Semver on npm with 25 CLI versions and a version line in the skill, two git tags and no changelog (5 of 15). Total 61.\n- Privy Wallets (server wallets, agent wallets, policy engine) (83): A public OpenAPI 3.1 document at api.privy.io/v1/openapi.json, 178 paths and 231 operations on 1 November, though its `info.version` is 0.0.1 (25). llms.txt with 400+ links and Markdown twins (10). The docs explain what each wallet action and policy field is for; we didn't read every reference page (14 of 20). Policy conditions are typed by field source and operator, with a `chain_type` on every policy (13 of 15). Ten named API error codes, each with troubleshooting steps, and examples in the docs, but no table of HTTP statuses (11 of 15). `/v1` paths and weekly product updates, but the OpenAPI version has never moved off 0.0.1 (10 of 15).\n\n### Agent ergonomics: Privy Wallets (server wallets, agent wallets, policy engine) +21\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- Privy Wallets (server wallets, agent wallets, policy engine) (81): No product MCP server (the docs MCP at docs.privy.io/mcp only searches documentation), so an agent works through the API, SDKs or the Agent CLI, and response sizing is ordinary REST (15 of 25). The OpenAPI file gives `cursor` and `limit` on the main lists (`/v1/wallets`, `/v1/users`, `/v1/policies`), filters such as `chain_type`, `address`, `user_id` and `include_archived` on wallets, and `include` flags elsewhere, but list routes such as `/v1/transactions` and `/v1/actions` take no paging parameters (18 of 20). Errors such as `policy_violation`, `insufficient_funds` and `transaction_broadcast_failure` come with recovery steps, and the guide says a failed broadcast is safe to retry (16 of 20). Idempotency keys on every state-changing wallet route, 24-hour window, 400 on a changed body (20). SDKs for Node (0.37.0), Python, Go, Rust, Ruby, Java, React and Flutter plus the Agent CLI, but requests on key-owned wallets also need an authorisation signature (12 of 15). 15+18+16+20+12 = 81.\n\n### Maintenance \u0026 community: Privy Wallets (server wallets, agent wallets, policy engine) +14\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- Privy Wallets (server wallets, agent wallets, policy engine) (80): @privy-io/node 0.37.0 on 26 October 2026, and a weekly product update on 16 October (30). Node SDK 0.29.0 to 0.37.0, nine releases between 17 August and 26 October, and weekly product updates on 7 and 14 August, 18 and 25 September and 2, 9 and 16 October (20). Weekly product updates and monthly rollups through September 2026; we didn't test a support channel (10 of 15). Current official SDKs in Node, Python, Go, Rust, Ruby and Java, plus React and Flutter (15). The Agent CLI is pre-1.0 (0.3.10). The Node SDK's CI workflows are in its public repository, but we couldn't see run results (5 of 10). 30+20+10+15+5 = 80. The 1 October note put 0.35.0 on 28 September; the changelog and tag date it 21 September.\n\n## Score by category\n\n| Category | Weight | FluxA AI Wallet | Privy Wallets (server wallets, agent wallets, policy engine) | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 53 | Privy Wallets (server wallets, agent wallets, policy engine) +33 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 83 | Privy Wallets (server wallets, agent wallets, policy engine) +22 |\n| Agent ergonomics | 13% (16.2 this run) | 60 | 81 | Privy Wallets (server wallets, agent wallets, policy engine) +21 |\n| Security \u0026 auth | 14% (17.5 this run) | 52 | 85 | Privy Wallets (server wallets, agent wallets, policy engine) +33 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 45 | 55 | Privy Wallets (server wallets, agent wallets, policy engine) +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 66 | 80 | Privy Wallets (server wallets, agent wallets, policy engine) +14 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 32 | 72 | Privy Wallets (server wallets, agent wallets, policy engine) +40 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **47 · D** | **72.3 · BB** | |\n\n## Facts side by side\n\n| Fact | FluxA AI Wallet | Privy Wallets (server wallets, agent wallets, policy engine) |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | FluxA Technology Pte. Ltd. | Privy (Stripe) |\n| Hosted endpoint | `https://walletapi.fluxapay.xyz` | `https://api.privy.io/v1` |\n| Transports | HTTP, stdio | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Freemium |\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 | none |\n| Tools exposed | 15 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-11-06 | 2026-10-26 |\n| Terms last updated | no document linked | 2025-12-16 |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | yes |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | yes |\n| Popularity | none | 296k npm/wk, 13k PyPI/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### Privy Wallets (server wallets, agent wallets, policy engine)\n\n- +2.3 on 1 November 2026: new evidence, correction\n- +0.1 on 27 October 2026 (B to BB): checklist\n- -0.2 on 8 October 2026 (BB to B): 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**Privy Wallets (server wallets, agent wallets, policy engine).** Default-deny policies with DENY precedence on recipients, values, contracts, calldata, typed data and time windows, enforced in AWS Nitro Enclaves. Database problems caused outages across API endpoints for 71 minutes on 18 September 2026, and rate limits aren't published as numbers.\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### Privy Wallets (server wallets, agent wallets, policy engine)\n\n1. Add a rule for every RPC method the agent needs; a wallet with a policy denies anything unlisted\n2. Pair a rolling cap with a lower per-transaction cap, since aggregations update only after signing\n3. Send an idempotency key on `/rpc`, `/transfer` and `/wallets` calls; reusing one with a changed body returns 400\n4. Set `maxValue` in React or `spendControls` in Node (0.37.0 or later) on the x402 client; the MPP guide shows no cap, so rely on wallet policies there\n5. Retry a `transaction_broadcast_failure`; don't retry a `policy_violation`\n\n## Tutorials\n\n- [Find an agent wallet by external ID with Privy](https://www.anchorterminal.com/tutorials/privy/), for Privy Wallets (server wallets, agent wallets, policy engine)\n\n## Questions\n\n### Which is better for AI agents, FluxA AI Wallet or Privy Wallets (server wallets, agent wallets, policy engine)?\n\nPrivy Wallets (server wallets, agent wallets, policy engine) scores 72.3 (BB) on agent readiness against FluxA AI Wallet's 47 (D), and leads in every scored category.\n\n### Do FluxA AI Wallet and Privy Wallets (server wallets, agent wallets, policy engine) need an API key?\n\nBoth take an API key or an OAuth sign-in.\n\n### Can an agent call FluxA AI Wallet and Privy Wallets (server wallets, agent wallets, policy engine) without installing anything?\n\nYes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Privy Wallets (server wallets, agent wallets, policy engine) at https://api.privy.io/v1.\n\n### Are FluxA AI Wallet and Privy Wallets (server wallets, agent wallets, policy engine) 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 Privy Wallets (server wallets, agent wallets, policy engine).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fluxa-ai-wallet\", \"b\": \"privy\"}`. From a terminal: `anchor compare fluxa-ai-wallet privy`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fluxa-ai-wallet.json and https://www.anchorterminal.com/api/v1/tools/privy.json\n\n## Other comparisons with FluxA AI Wallet or Privy Wallets (server wallets, agent wallets, policy engine)\n\n- [Agentcard vs FluxA AI Wallet](https://www.anchorterminal.com/compare/agentcard-vs-fluxa-ai-wallet.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- [Circle Wallets (Agent Wallets, Programmable Wallets) vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/circle-wallets-vs-privy.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- [Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-privy.md)\n- [Kite Agent Passport vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/kite-agent-passport-vs-privy.md)\n- [Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/openfort-vs-privy.md)\n- [Privy Wallets (server wallets, agent wallets, policy engine) vs Sponge Wallet](https://www.anchorterminal.com/compare/privy-vs-sponge-wallet.md)\n- [Privy Wallets (server wallets, agent wallets, policy engine) vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/privy-vs-turnkey-agentic-wallets.md)\n- [Circle Gateway Nanopayments vs FluxA AI Wallet](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-ai-wallet.md)\n- [FluxA AgentMarket vs FluxA AI Wallet](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-fluxa-ai-wallet.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 Payman Genie MCP](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman.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- [Agentcard vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/agentcard-vs-privy.md)\n- [FluxA AI Wallet vs Agent Vault by Self](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault.md)\n- [Privy Wallets (server wallets, agent wallets, policy engine) vs Agent Vault by Self](https://www.anchorterminal.com/compare/privy-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 Privy Wallets (server wallets, agent wallets, policy engine)", "url": "" } ], "description": "Privy Wallets scores 72.3 (BB) to FluxA AI Wallet's 47 (D) for x402 payments. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "FluxA AI Wallet D 47", "Privy Wallets (server wallets, agent wallets, policy engine) BB 72.3", "scores" ], "h1": "FluxA AI Wallet vs Privy Wallets (server wallets, agent wallets, policy engine)", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fluxa-ai-wallet-vs-privy", "published": "2026-10-01", "section": "tools", "title": "FluxA AI Wallet vs Privy Wallets for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy" }, "tokens": { "markdown": 6450, "slim": 1480 }, "version": 1 }