{ "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": "FluxA AI Wallet scores 47 (D) on agent readiness against Sponge Wallet's 43.5 (E), and leads in 4 of 7 scored categories. Sponge Wallet leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "sponge-wallet", "name": "Sponge Wallet", "vendor": "Sponge Inc.", "vendorUrl": "https://paysponge.com", "kind": "http-api", "category": "agent-wallets", "summary": "Sponge Wallet is a hosted wallet for AI agents. It holds stablecoins on Ethereum, Base, Tempo and Solana, pays x402 and MPP endpoints, issues virtual cards, and is reached by a REST API, an MCP server, SDKs and a CLI.", "url": "https://www.anchorterminal.com/tools/sponge-wallet", "markdownUrl": "https://www.anchorterminal.com/tools/sponge-wallet.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sponge-wallet.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sponge-wallet.json", "dns": "sponge-wallet.grade.anchorterminal.com", "license": "Proprietary service under Sponge's terms of service. The SDK and CLI packages on npm are MIT, and the repository they name is private", "transports": [ "http" ], "remoteUrl": "https://api.wallet.paysponge.com", "packages": [ { "registry": "npm", "name": "@paysponge/sdk" }, { "registry": "npm", "name": "spongewallet" }, { "registry": "pypi", "name": "paysponge" } ], "auth": "mixed", "authNotes": "Self-serve. An agent calls `POST /api/agents/register` with no credential and, with `agentFirst`, receives an agent API key at once. A person claims the wallet later through a claim URL. Requests carry the key as a bearer token plus a `Sponge-Version` header. Master keys, created in the dashboard, manage agents. The MCP server also accepts OAuth from app connectors.", "pricing": "free", "pricingNotes": "No fee schedule for the wallet was found. The home page's structured data lists a price of 0, a wallet needs no card or contract to start, and network and venue costs apply. Sponge Card (US) has no annual fee and charges 1 per cent on international transactions (https://paysponge.com/legal/sponge-card-terms-us, checked 2026-10-09). Fees on swaps, bridges, bank transfers and onramps were not found.", "priceSummary": "Free", "where": "hosted", "x402": { "level": "partial", "evidence": "The wallet pays x402 endpoints through `POST /api/x402/fetch`, `wallet.x402Fetch()` and `spongewallet pay x402`, pays MPP endpoints on Tempo, and creates x402 payment links. Sponge's own wallet API is not paid over either protocol (https://docs.paysponge.com/wallet/x402-payments.md; https://docs.paysponge.com/wallet/mpp-payments.md, checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 126, "pypiWeekly": 20, "asOf": "2026-10-09" }, "docsUrl": "https://docs.paysponge.com", "llmsTxt": "https://docs.paysponge.com/llms.txt", "openapi": "https://docs.paysponge.com/api-reference/public-openapi.json", "capabilities": [ "wallet.onchain", "wallet.spend-limits", "payments.x402", "payments.card", "wallet.custody" ], "tags": [ "hosted", "free", "openapi", "llms-txt", "mcp", "typescript", "python", "cli", "wallet", "x402", "mpp", "virtual-cards", "stablecoins", "closed-source", "skills" ], "lastRelease": "2026-07-07", "graded": true, "anchor": { "graded": true, "score": 43.5, "grade": "E", "agentReady": false, "rank": 1252, "ranked": true, "rankOf": 1513, "categoryRank": 12, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 43, "maintenance": 27, "payments": 70, "reliability": 13, "schema": 66, "security": 48, "transparency": 42 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "An agent can register a wallet with one unauthenticated call and pay x402 or MPP endpoints under daily, weekly and monthly limits enforced on Sponge's servers. No status page, rate limits, fee schedule, custody statement or security contact was found, the terms run to eleven short clauses, and the SDK was last published on 7 July 2026.", "bestFor": "A developer who wants an agent to hold stablecoins and pay x402 or MPP endpoints within minutes, with cards, bank rails and Hyperliquid or Polymarket trading behind the same key.", "strengths": [ "`POST /api/agents/register` with `agentFirst` returns an agent key at once, and a person claims the wallet later through a claim URL", "Daily, weekly and monthly spending limits are set per agent and enforced server-side, with address allowlists that return 403", "One wallet pays x402 and MPP endpoints, opens MPP sessions on Tempo and creates x402 payment links", "Agent keys cover one agent and can be regenerated. Master keys create agents and, per the docs, never touch wallets", "Public OpenAPI 3.0.3 file with 57 operations, llms.txt, Markdown docs and a 73 KB skill file written for agents" ], "weaknesses": [ "No status page, SLA or numeric rate limit was found, and the terms say the service may be offered in beta", "Who holds the wallet keys is not stated in the docs or the terms. The skill file calls the wallet managed", "The terms of 30 June 2026 are eleven short clauses that do not mention wallets, funds, custody or fees", "No security.txt, disclosure policy, certification or bug bounty was found", "`@paysponge/sdk` was last published on 7 July 2026 after 115 versions in five months. The source repository is private", "The transfers page separates `wallet.transfer()` from enforced helpers that apply allowlists and limits, while another page says limits apply to every transfer" ], "agentNotes": [ "Send `Sponge-Version` on every REST request. The skill file marks it required and the API answers with version status headers", "Use `evmTransfer` and `solanaTransfer`, the helpers the docs describe as enforcing allowlists and spending limits, not plain `transfer`", "Store the `apiKey` from registration at once. It is returned a single time, and losing it means registering again", "Call `GET /api/discover/{serviceId}` before `POST /api/paid/fetch`. The skill file says direct service URLs fail with auth errors", "Treat `card details` output as secret. It returns an encrypted card number and CVC with a one-time `secret_key`" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 43.5 } ], "editorialScores": { "ergonomics": 43, "maintenance": 27, "payments": 70, "reliability": 13, "schema": 66, "security": 48, "transparency": 27 }, "provenanceScore": 57, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "lastMoved": "2026-10-27", "oldest": "2026-10-09", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install @paysponge/sdk", "http": "curl -sS -X POST https://api.wallet.paysponge.com/api/agents/register -H \"Sponge-Version: 0.2.2\" -H \"Content-Type: application/json\" -d '{\"name\":\"YourAgentName\",\"agentFirst\":true}'", "claudeCode": "claude mcp add -s user --transport http sponge https://api.wallet.paysponge.com/mcp --header \"Authorization: Bearer \u003cSPONGE_API_KEY\u003e\"" }, "letme": { "capability": "https://letme.dev/wallet.onchain", "tool": "https://letme.dev/sponge-wallet" }, "area": "payments", "unitPrices": [ { "item": "Sponge Card international transaction (US terms)", "unit": "pct", "usd": 1, "note": "no annual fee, 0 per cent APR" } ], "provenance": { "legalEntity": "Sponge Inc.", "domain": "paysponge.com", "domainRegistered": "2026-01-09", "endpointOnVendorDomain": true, "terms": "https://paysponge.com/terms", "privacy": "https://paysponge.com/privacy", "statusPage": "", "changelog": "", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The terms of service (updated 30 June 2026) say they govern the Sponge platform and related services. They are eleven short clauses, name no legal entity or address, and choose the laws of the United States.", "The site footer names Sponge Inc. No company address or registration was found on the pages read.", "The privacy policy (updated 30 June 2026) covers the platform and related services. A separate account opening privacy notice and card terms cover the Sponge Card, whose issuer is Rain.", "The API and MCP server answer at api.wallet.paysponge.com and the dashboard at wallet.paysponge.com. The MCP resource metadata names spongewallet.com for documentation.", "paysponge.com/.well-known/security.txt returned 404. No status page or changelog was found.", "RDAP for paysponge.com gives a registration date of 2026-01-09." ], "score": 57 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sponge-wallet.json", "live": { "slug": "sponge-wallet", "probe": { "target": "https://api.wallet.paysponge.com", "method": "get", "lastAt": "2026-11-08T14:48:13.106341985Z", "lastOk": true, "lastStatus": 404, "lastMs": 217, "authRequired": false, "uptime24h": 100, "uptime30d": 99.93, "p50ms24h": 229, "p95ms24h": 512, "samples24h": 242, "samples30d": 7495, "days": [ { "date": "2026-10-09", "probes": 169, "ok": 169 }, { "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": 244 }, { "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 } ], "outages": [ { "start": "2026-10-27T22:43:25.301565276Z", "end": "2026-10-27T23:11:45.638315091Z", "note": "HTTP 503 server error" } ], "since": "2026-10-09T00:00:00Z" }, "versions": [ { "registry": "npm", "name": "@paysponge/sdk", "version": "0.1.148", "seenAt": "2026-11-08T01:39:36.241156874Z" }, { "registry": "npm", "name": "spongewallet", "version": "0.1.128", "seenAt": "2026-11-08T01:39:36.665434906Z" }, { "registry": "pypi", "name": "paysponge", "version": "0.1.5", "released": "2026-05-17", "seenAt": "2026-11-08T01:39:38.442261514Z" } ], "npmWeekly": 165, "pypiWeekly": 13, "securityTxt": { "url": "https://paysponge.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:05.662972927Z" }, "llmsTxt": { "url": "https://docs.paysponge.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:34:01.309507292Z" }, "domain": { "domain": "paysponge.com", "registered": "2026-01-09", "source": "https://rdap.verisign.com/com/v1/domain/paysponge.com", "checkedAt": "2026-11-08T14:50:35.507580102Z" }, "pages": [ { "url": "https://paysponge.com/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:16:10.005158118Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "e0bb0a039144" }, { "url": "https://paysponge.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:16:12.389544542Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "ec8eb426955c" } ], "mcpTools": { "url": "https://api.wallet.paysponge.com/mcp", "checkedAt": "2026-11-08T02:01:58.398889803Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-07T01:48:05.83001726Z" }, "updatedAt": "2026-11-08T14:50:35.507580102Z" }, "streak": { "days": 12, "from": "2026-10-27", "last": { "kind": "outage", "date": "2026-10-27", "what": "HTTP 503 server error", "lasted": "28 minutes" }, "best": 18 } }, "edges": [ { "by": 39, "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": "`@paysponge/sdk` 0.1.147 and `spongewallet` 0.1.127 were published on 7 July 2026, 94 days before this check. The docs sitemap's newest date is 27 May 2026 and the wallet skill file was last modified on 23 June 2026 (10 of 30). No release or dated changelog entry falls in the last 90 days (0). The service is closed and the repository named in the packages, github.com/paysponge/sponge, is private. Support is a Discord server and a contact address, neither tested, and no changelog was found (4 of 15). Official SDKs exist in TypeScript and Python. The TypeScript SDK had 115 versions between 31 January and 7 July 2026 and the Python package six, all in May 2026 (10 of 15). The SDK has six runtime dependencies. CI is not visible because the repository is private (3 of 10)." }, "scores": { "a": 66, "b": 27 } }, { "by": 25, "category": "payments", "leads": "sponge-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. The wallet pays x402 and MPP endpoints and creates x402 payment links so that another agent can pay its holder, and Sponge's separate Gateway product puts x402 and MPP in front of a seller's API. The wallet API itself is not paid over either, so the merchant step (25 of 40). No fee schedule for the wallet was found. The home page's structured data lists a price of 0, and the Sponge Card terms for the US give no annual fee and 1 per cent on international transactions. Fees on swaps, bridges, bank transfers and onramps were not found (5 of 20). A wallet costs nothing to create and needs no card, and the SDK defines a `claim_signup_bonus` tool that sends 1 USDC on Base (20). `POST /api/agents/register` needs no authentication and with `agentFirst` returns an API key at once, and `npx spongewallet init` does the same from a terminal. A person claims the agent later (20)." }, "scores": { "a": 45, "b": 70 } }, { "by": 17, "category": "ergonomics", "leads": "fluxa-ai-wallet", "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": "`@paysponge/sdk` 0.1.147 defines 53 tools for the MCP server, from `get_balance` to `polymarket`, which is the more-than-30 band (5). A second, trading-only server at `/trade/mcp` exposes seven tools, and `get_balance` can be narrowed by chain or to USDC (5 back, 10 of 25). We did not connect to the live server, so the count is from the package. Transaction history and MPP sessions take a `limit` and a chain or status filter and service discovery takes `limit` and `offset`. No cursor was found (8 of 20). Errors are an HTTP status and `{\"error\":\"message\"}`, with seven statuses explained and no list of machine-readable codes (9 of 20). No idempotency key was found for transfers, swaps or bank sends. 409 is described as a duplicate action, creating a virtual account is described as idempotent, and the SDK's tool definitions carry no read-only or destructive annotations (4 of 20). SDKs in TypeScript and Python, a CLI, and wallets created on every supported chain with no parameters. The Python package is at 0.1.5 from May 2026, and spending limits and banking are documented for TypeScript only (12 of 15)." }, "scores": { "a": 60, "b": 43 } }, { "by": 10, "category": "transparency", "leads": "sponge-wallet", "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": "A closed service. The SDK and CLI are MIT on npm, and the repository they name is private. The terms of service, updated 30 June 2026, are eleven short clauses that describe the service as AI-powered functionality and do not mention wallets, funds, custody, fees or API use (10 of 30). The privacy policy of the same date lists prompts, usage data and IP addresses, names no provider, gives no retention period beyond as long as necessary, and does not mention payment, card, bank or identity data. Separate card terms and an account opening privacy notice cover the Sponge Card (8 of 30). The API reports version status and a minimum version in response headers. No deprecation policy or dated notice was found (3 of 20). Basis Theory is named in the terms, Rain as card issuer on the home page, and Persona, Stripe and Coinbase in the docs, with no subprocessor list or data location. The CLI sends usage events to PostHog, which the npm README discloses, and no opt-out setting was found in the package (6 of 20)." }, "scores": { "a": 32, "b": 42 } }, { "by": 7, "category": "reliability", "leads": "fluxa-ai-wallet", "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": "Graded as a hosted service on the REST API and the MCP server at api.wallet.paysponge.com. No status page was found. The site and docs link none and status.paysponge.com did not resolve (0). With no readable incident history the record takes the default (5). No rate limit with numbers was found in the docs, the OpenAPI file or the skill file (0). The skill file lists 429 as rate limited with the advice to back off and retry, and 409 for a duplicate action. No `Retry-After` header, backoff schedule or idempotency key is documented for transfers (4 of 15). No SLA was found (0). The terms say the service may be offered in beta and may change or be discontinued at any time, the SDK and CLI are at 0.1.x, and Sponge Card is labelled a beta preview. The wallet API itself carries no beta label (4 of 10)." }, "scores": { "a": 20, "b": 13 } }, { "by": 5, "category": "schema", "leads": "sponge-wallet", "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.0.3 file at docs.paysponge.com/api-reference/public-openapi.json with 51 paths and 57 operations. It leaves out endpoints the skill file documents, among them `/api/agents/register`, `/api/paid/fetch`, `/api/discover`, the bank routes and `/api/payment-links` (20 of 25). llms.txt, a Markdown twin of each docs page and two skill files for agents (10). Most operation descriptions in the OpenAPI file repeat the title, such as \"Get wallet details via GET.\", while the skill file and the SDK's 53 tool definitions say when to use each call (12 of 20). The spec has 48 enums and 123 required lists. Amounts travel as strings and the `hyperliquid` and `polymarket` tools take an action name plus loosely typed arguments (10 of 15). The docs carry TypeScript, Python and curl examples for each workflow. Errors are a seven-row table in the skill file, the OpenAPI file documents only 200 and 204 responses, and the `SpongeApiError` codes are not listed (8 of 15). Every request carries a `Sponge-Version` header and the API returns version status and minimum-version headers. No changelog was found (6 of 15)." }, "scores": { "a": 61, "b": 66 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "FluxA Technology Pte. Ltd.", "b": "Sponge Inc.", "name": "Vendor" }, { "a": "https://walletapi.fluxapay.xyz", "b": "https://api.wallet.paysponge.com", "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": "Free", "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": "Proprietary service under Sponge's terms of service. The SDK and CLI packages on npm are MIT, and the repository they name is private", "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-07-07", "name": "Last release" }, { "a": "no document linked", "b": "2026-06-30", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-06-30", "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": "not found in the text", "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": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "126 npm/wk, 20 PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "FluxA AI Wallet scores 47 (D) on agent readiness against Sponge Wallet's 43.5 (E), and leads in 4 of 7 scored categories. Sponge Wallet leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, FluxA AI Wallet or Sponge Wallet?" }, { "answer": "Both take an API key or an OAuth sign-in.", "question": "Do FluxA AI Wallet and Sponge Wallet need an API key?" }, { "answer": "Yes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Sponge Wallet at https://api.wallet.paysponge.com.", "question": "Can an agent call FluxA AI Wallet and Sponge Wallet 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 Sponge Wallet.", "question": "Are FluxA AI Wallet and Sponge Wallet open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 20 against 13", "Agent ergonomics, 60 against 43", "Maintenance \u0026 community, 66 against 27" ], "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": [ "Schema \u0026 documentation, 66 against 61", "Payments \u0026 pricing, 70 against 45", "Transparency \u0026 trust, 42 against 32" ], "also": null, "goodFor": "A developer who wants an agent to hold stablecoins and pay x402 or MPP endpoints within minutes, with cards, bank rails and Hyperliquid or Polymarket trading behind the same key.", "slug": "sponge-wallet", "watchFor": "No status page, SLA or numeric rate limit was found, and the terms say the service may be offered in beta" } ], "history": { "fluxa-ai-wallet": null, "sponge-wallet": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.3, "from": 43.2, "fromGrade": "E", "to": 43.5, "toGrade": "E" } ] }, "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/agentcard-vs-sponge-wallet.json", "title": "Agentcard vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/agentcard-vs-sponge-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-sponge-wallet.json", "title": "Circle Wallets (Agent Wallets, Programmable Wallets) vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/circle-wallets-vs-sponge-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/coinbase-cdp-agentkit-vs-sponge-wallet.json", "title": "Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-sponge-wallet" }, { "json": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-sponge-wallet.json", "title": "Kite Agent Passport vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/kite-agent-passport-vs-sponge-wallet" }, { "json": "https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet.json", "title": "Openfort vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet" }, { "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/sponge-wallet-vs-turnkey-agentic-wallets.json", "title": "Sponge Wallet vs Turnkey Agentic Wallets", "url": "https://www.anchorterminal.com/compare/sponge-wallet-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-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-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/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/self-agent-vault-vs-sponge-wallet.json", "title": "Agent Vault by Self vs Sponge Wallet", "url": "https://www.anchorterminal.com/compare/self-agent-vault-vs-sponge-wallet" } ], "panel": null, "scores": [ { "by": 7, "edge": "fluxa-ai-wallet", "fluxa-ai-wallet": 20, "key": "reliability", "name": "Reliability", "sponge-wallet": 13, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 5, "edge": "sponge-wallet", "fluxa-ai-wallet": 61, "key": "schema", "name": "Schema \u0026 documentation", "sponge-wallet": 66, "weight": 13 }, { "by": 17, "edge": "fluxa-ai-wallet", "fluxa-ai-wallet": 60, "key": "ergonomics", "name": "Agent ergonomics", "sponge-wallet": 43, "weight": 13 }, { "by": 4, "edge": "fluxa-ai-wallet", "fluxa-ai-wallet": 52, "key": "security", "name": "Security \u0026 auth", "sponge-wallet": 48, "weight": 14 }, { "by": 25, "edge": "sponge-wallet", "fluxa-ai-wallet": 45, "key": "payments", "name": "Payments \u0026 pricing", "sponge-wallet": 70, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 39, "edge": "fluxa-ai-wallet", "fluxa-ai-wallet": 66, "key": "maintenance", "name": "Maintenance \u0026 community", "sponge-wallet": 27, "weight": 7 }, { "by": 10, "edge": "sponge-wallet", "fluxa-ai-wallet": 32, "key": "transparency", "name": "Transparency \u0026 trust", "sponge-wallet": 42, "weight": 7 } ], "summary": "FluxA AI Wallet scores 47 (D) on agent readiness against Sponge Wallet's 43.5 (E), and leads in 4 of 7 scored categories. Sponge Wallet leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust. 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.", "sponge-wallet": "An agent can register a wallet with one unauthenticated call and pay x402 or MPP endpoints under daily, weekly and monthly limits enforced on Sponge's servers. No status page, rate limits, fee schedule, custody statement or security contact was found, the terms run to eleven short clauses, and the SDK was last published on 7 July 2026." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet", "json": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet.min.md" }, "markdown": "FluxA AI Wallet scores 47 (D) on agent readiness against Sponge Wallet's 43.5 (E), and leads in 4 of 7 scored categories. Sponge Wallet leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust. 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- Sponge Wallet: grade E, 43.5/100, rank #1252 of 1513. Markdown https://www.anchorterminal.com/tools/sponge-wallet.md · JSON https://www.anchorterminal.com/api/v1/tools/sponge-wallet.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\nAhead on:\n- Reliability, 20 against 13\n- Agent ergonomics, 60 against 43\n- Maintenance \u0026 community, 66 against 27\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### Sponge Wallet (E)\n\nGood for: A developer who wants an agent to hold stablecoins and pay x402 or MPP endpoints within minutes, with cards, bank rails and Hyperliquid or Polymarket trading behind the same key.\n\nAhead on:\n- Schema \u0026 documentation, 66 against 61\n- Payments \u0026 pricing, 70 against 45\n- Transparency \u0026 trust, 42 against 32\n\nWatch for: No status page, SLA or numeric rate limit was found, and the terms say the service may be offered in beta\n\n\n## Why the edge\n\n### Maintenance \u0026 community: FluxA AI Wallet +39\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- Sponge Wallet (27): `@paysponge/sdk` 0.1.147 and `spongewallet` 0.1.127 were published on 7 July 2026, 94 days before this check. The docs sitemap's newest date is 27 May 2026 and the wallet skill file was last modified on 23 June 2026 (10 of 30). No release or dated changelog entry falls in the last 90 days (0). The service is closed and the repository named in the packages, github.com/paysponge/sponge, is private. Support is a Discord server and a contact address, neither tested, and no changelog was found (4 of 15). Official SDKs exist in TypeScript and Python. The TypeScript SDK had 115 versions between 31 January and 7 July 2026 and the Python package six, all in May 2026 (10 of 15). The SDK has six runtime dependencies. CI is not visible because the repository is private (3 of 10).\n\n### Payments \u0026 pricing: Sponge Wallet +25\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- Sponge Wallet (70): 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 and MPP endpoints and creates x402 payment links so that another agent can pay its holder, and Sponge's separate Gateway product puts x402 and MPP in front of a seller's API. The wallet API itself is not paid over either, so the merchant step (25 of 40). No fee schedule for the wallet was found. The home page's structured data lists a price of 0, and the Sponge Card terms for the US give no annual fee and 1 per cent on international transactions. Fees on swaps, bridges, bank transfers and onramps were not found (5 of 20). A wallet costs nothing to create and needs no card, and the SDK defines a `claim_signup_bonus` tool that sends 1 USDC on Base (20). `POST /api/agents/register` needs no authentication and with `agentFirst` returns an API key at once, and `npx spongewallet init` does the same from a terminal. A person claims the agent later (20).\n\n### Agent ergonomics: FluxA AI Wallet +17\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- Sponge Wallet (43): `@paysponge/sdk` 0.1.147 defines 53 tools for the MCP server, from `get_balance` to `polymarket`, which is the more-than-30 band (5). A second, trading-only server at `/trade/mcp` exposes seven tools, and `get_balance` can be narrowed by chain or to USDC (5 back, 10 of 25). We did not connect to the live server, so the count is from the package. Transaction history and MPP sessions take a `limit` and a chain or status filter and service discovery takes `limit` and `offset`. No cursor was found (8 of 20). Errors are an HTTP status and `{\"error\":\"message\"}`, with seven statuses explained and no list of machine-readable codes (9 of 20). No idempotency key was found for transfers, swaps or bank sends. 409 is described as a duplicate action, creating a virtual account is described as idempotent, and the SDK's tool definitions carry no read-only or destructive annotations (4 of 20). SDKs in TypeScript and Python, a CLI, and wallets created on every supported chain with no parameters. The Python package is at 0.1.5 from May 2026, and spending limits and banking are documented for TypeScript only (12 of 15).\n\n### Transparency \u0026 trust: Sponge Wallet +10\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- Sponge Wallet (42): A closed service. The SDK and CLI are MIT on npm, and the repository they name is private. The terms of service, updated 30 June 2026, are eleven short clauses that describe the service as AI-powered functionality and do not mention wallets, funds, custody, fees or API use (10 of 30). The privacy policy of the same date lists prompts, usage data and IP addresses, names no provider, gives no retention period beyond as long as necessary, and does not mention payment, card, bank or identity data. Separate card terms and an account opening privacy notice cover the Sponge Card (8 of 30). The API reports version status and a minimum version in response headers. No deprecation policy or dated notice was found (3 of 20). Basis Theory is named in the terms, Rain as card issuer on the home page, and Persona, Stripe and Coinbase in the docs, with no subprocessor list or data location. The CLI sends usage events to PostHog, which the npm README discloses, and no opt-out setting was found in the package (6 of 20).\n\n### Reliability: FluxA AI Wallet +7\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- Sponge Wallet (13): Graded as a hosted service on the REST API and the MCP server at api.wallet.paysponge.com. No status page was found. The site and docs link none and status.paysponge.com did not resolve (0). With no readable incident history the record takes the default (5). No rate limit with numbers was found in the docs, the OpenAPI file or the skill file (0). The skill file lists 429 as rate limited with the advice to back off and retry, and 409 for a duplicate action. No `Retry-After` header, backoff schedule or idempotency key is documented for transfers (4 of 15). No SLA was found (0). The terms say the service may be offered in beta and may change or be discontinued at any time, the SDK and CLI are at 0.1.x, and Sponge Card is labelled a beta preview. The wallet API itself carries no beta label (4 of 10).\n\n### Schema \u0026 documentation: Sponge Wallet +5\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- Sponge Wallet (66): A public OpenAPI 3.0.3 file at docs.paysponge.com/api-reference/public-openapi.json with 51 paths and 57 operations. It leaves out endpoints the skill file documents, among them `/api/agents/register`, `/api/paid/fetch`, `/api/discover`, the bank routes and `/api/payment-links` (20 of 25). llms.txt, a Markdown twin of each docs page and two skill files for agents (10). Most operation descriptions in the OpenAPI file repeat the title, such as \"Get wallet details via GET.\", while the skill file and the SDK's 53 tool definitions say when to use each call (12 of 20). The spec has 48 enums and 123 required lists. Amounts travel as strings and the `hyperliquid` and `polymarket` tools take an action name plus loosely typed arguments (10 of 15). The docs carry TypeScript, Python and curl examples for each workflow. Errors are a seven-row table in the skill file, the OpenAPI file documents only 200 and 204 responses, and the `SpongeApiError` codes are not listed (8 of 15). Every request carries a `Sponge-Version` header and the API returns version status and minimum-version headers. No changelog was found (6 of 15).\n\n## Score by category\n\n| Category | Weight | FluxA AI Wallet | Sponge Wallet | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 20 | 13 | FluxA AI Wallet +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 61 | 66 | Sponge Wallet +5 |\n| Agent ergonomics | 13% (16.2 this run) | 60 | 43 | FluxA AI Wallet +17 |\n| Security \u0026 auth | 14% (17.5 this run) | 52 | 48 | FluxA AI Wallet +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 45 | 70 | Sponge Wallet +25 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 66 | 27 | FluxA AI Wallet +39 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 32 | 42 | Sponge Wallet +10 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **47 · D** | **43.5 · E** | |\n\n## Facts side by side\n\n| Fact | FluxA AI Wallet | Sponge Wallet |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | FluxA Technology Pte. Ltd. | Sponge Inc. |\n| Hosted endpoint | `https://walletapi.fluxapay.xyz` | `https://api.wallet.paysponge.com` |\n| Transports | HTTP, stdio | HTTP |\n| Auth | OAuth or key | OAuth or key |\n| Pricing | Pay per use | Free |\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 | Proprietary service under Sponge's terms of service. The SDK and CLI packages on npm are MIT, and the repository they name is private |\n| Tools exposed | 15 | none |\n| Read-only variant documented | no | no |\n| llms.txt | no | yes |\n| Last release | 2026-11-06 | 2026-07-07 |\n| Terms last updated | no document linked | 2026-06-30 |\n| Privacy policy last updated | no document linked | 2026-06-30 |\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 | not found in the text |\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 | not found in the text |\n| Popularity | none | 126 npm/wk, 20 PyPI/wk |\n| Agent reviews | none | 3/5 (4) |\n\n## How the scores have moved\n\n### FluxA AI Wallet\n\nNo score change since it was listed.\n\n### Sponge Wallet\n\n- +0.3 on 27 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**Sponge Wallet.** An agent can register a wallet with one unauthenticated call and pay x402 or MPP endpoints under daily, weekly and monthly limits enforced on Sponge's servers. No status page, rate limits, fee schedule, custody statement or security contact was found, the terms run to eleven short clauses, and the SDK was last published on 7 July 2026.\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### Sponge Wallet\n\n1. Send `Sponge-Version` on every REST request. The skill file marks it required and the API answers with version status headers\n2. Use `evmTransfer` and `solanaTransfer`, the helpers the docs describe as enforcing allowlists and spending limits, not plain `transfer`\n3. Store the `apiKey` from registration at once. It is returned a single time, and losing it means registering again\n4. Call `GET /api/discover/{serviceId}` before `POST /api/paid/fetch`. The skill file says direct service URLs fail with auth errors\n5. Treat `card details` output as secret. It returns an encrypted card number and CVC with a one-time `secret_key`\n\n## Questions\n\n### Which is better for AI agents, FluxA AI Wallet or Sponge Wallet?\n\nFluxA AI Wallet scores 47 (D) on agent readiness against Sponge Wallet's 43.5 (E), and leads in 4 of 7 scored categories. Sponge Wallet leads on schema \u0026 documentation, payments \u0026 pricing and transparency \u0026 trust.\n\n### Do FluxA AI Wallet and Sponge Wallet 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 Sponge Wallet without installing anything?\n\nYes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Sponge Wallet at https://api.wallet.paysponge.com.\n\n### Are FluxA AI Wallet and Sponge Wallet 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 Sponge Wallet.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"fluxa-ai-wallet\", \"b\": \"sponge-wallet\"}`. From a terminal: `anchor compare fluxa-ai-wallet sponge-wallet`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fluxa-ai-wallet.json and https://www.anchorterminal.com/api/v1/tools/sponge-wallet.json\n\n## Other comparisons with FluxA AI Wallet or Sponge Wallet\n\n- [Agentcard vs FluxA AI Wallet](https://www.anchorterminal.com/compare/agentcard-vs-fluxa-ai-wallet.md)\n- [Agentcard vs Sponge Wallet](https://www.anchorterminal.com/compare/agentcard-vs-sponge-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 Sponge Wallet](https://www.anchorterminal.com/compare/circle-wallets-vs-sponge-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- [Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Sponge Wallet](https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-sponge-wallet.md)\n- [Kite Agent Passport vs Sponge Wallet](https://www.anchorterminal.com/compare/kite-agent-passport-vs-sponge-wallet.md)\n- [Openfort vs Sponge Wallet](https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet.md)\n- [Privy Wallets (server wallets, agent wallets, policy engine) vs Sponge Wallet](https://www.anchorterminal.com/compare/privy-vs-sponge-wallet.md)\n- [Sponge Wallet vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/sponge-wallet-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 Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.md)\n- [FluxA AI Wallet vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets.md)\n- [FluxA AI Wallet vs Agent Vault by Self](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault.md)\n- [Agent Vault by Self vs Sponge Wallet](https://www.anchorterminal.com/compare/self-agent-vault-vs-sponge-wallet.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 Sponge Wallet", "url": "" } ], "description": "FluxA AI Wallet scores 47 (D) to Sponge Wallet's 43.5 (E) for x402 payments. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "FluxA AI Wallet D 47", "Sponge Wallet E 43.5", "scores" ], "h1": "FluxA AI Wallet vs Sponge Wallet", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/fluxa-ai-wallet-vs-sponge-wallet", "published": "2026-10-01", "section": "tools", "title": "FluxA AI Wallet vs Sponge Wallet for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet" }, "tokens": { "markdown": 6100, "slim": 1280 }, "version": 1 }