# FluxA AI Wallet vs Turnkey Agentic Wallets

> Turnkey Agentic Wallets scores 74.7 (BB) to FluxA AI Wallet's 47 (D) for x402 payments. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets
- Markdown: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets.md (~6,700 tokens)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-07

Turnkey Agentic Wallets scores 74.7 (BB) on agent readiness against FluxA AI Wallet's 47 (D), and leads in every scored category. Both do x402 payments.

- 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
- Turnkey Agentic Wallets: grade BB, 74.7/100, rank #77 of 1513. Markdown https://www.anchorterminal.com/tools/turnkey-agentic-wallets.md · JSON https://www.anchorterminal.com/api/v1/tools/turnkey-agentic-wallets.json
- Best agent wallets and spending controls: https://www.anchorterminal.com/best/agent-wallets/index.md
- All 77 wallets comparisons: https://www.anchorterminal.com/compare/agent-wallets/index.md

## Which one, for what

### FluxA AI Wallet (D)

Good 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.

Also in its favour:
- Runs on your own machine
- Open source
- No incidents deducted, where Turnkey Agentic Wallets loses 3 points for them

Watch 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

### Turnkey Agentic Wallets (BB)

Good for: A company that wants agents to sign from its own wallets under rules checked in an enclave, with a person co-approving large transactions, across EVM, Solana, Bitcoin, Tron and other chains.

Ahead on:
- Reliability, 83 against 20
- Schema & documentation, 79 against 61
- Agent ergonomics, 77 against 60
- Security & auth, 85 against 52
- Payments & pricing, 58 against 45
- Maintenance & community, 83 against 66
- Transparency & trust, 73 against 32

Also in its favour:
- Agent-ready, a grade of BB or better

Watch for: Documented policy conditions cap value per transaction only. Rolling-window Velocity Controls appear in the SDK clients but not in the docs


## Why the edge

### Reliability: Turnkey Agentic Wallets +63

- 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.
- Turnkey Agentic Wallets (83): Status page at turnkey-status.com on Atlassian Statuspage with 23 components and 90-day uptime bars (20). Between 3 August and 1 November 2026 it lists nine incidents. Signing endpoints, `sign_raw_payload` and `sign_transaction` among them, returned elevated errors for 5 hours 9 minutes on 27 August (00:44 to 05:53 EDT), marked minor, with "a subset of signing requests" rejected. SMS authentication had issues from 6 August and was resolved at 02:36 EDT on 7 August, marked critical, on the Authentication (SMS) component, outside the path an agent's API key uses. Webhook delays (15 August, 15 September) and broadcast failures traced to upstream RPC providers (31 August, 2 September) were partial. Three incidents since 17 October, SMS and email OTP delays of 45 minutes on 28 October, new Earn vault deployments blocked from 28 to 29 October and Aave V3 vaults hidden from Earn discovery on 29 and 30 October, are marked with no impact and leave signing untouched. The 27 July request failures have left the window. Read the way partial and degraded incidents on resend and pinecone were read on 1 November, a subset of requests on one path counts as minor, as stripe-mcp's payout errors of 6 August and pinecone's control-plane errors of 1 September did, so minor incidents only, 20 rather than the between-band 12 earlier checks gave (20). Rate limits are published as 1 request a second on Free and Pay-as-you-go, 3 on Pro and up to 60 on Enterprise, with 10 a second for each sub-organisation and separate buckets for broadcast and balance calls (15). The docs describe 429 handling with exponential backoff and jitter and say submissions are idempotent by body fingerprint, but "The API does not return rate-limit or `Retry-After` headers" (13 of 15). SLAs are listed on the Enterprise plan with no published terms (5 of 10). The API is generally available and the agent skills are at 1.0.0 (10). 20+20+15+13+5+10 = 83.

### Transparency & trust: Turnkey Agentic Wallets +41

- 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.
- Turnkey Agentic Wallets (73): A closed service under published terms of service, updated 6 August 2026, with the SDKs, CLI and agent skills under Apache-2.0 and QuorumOS open source (18 of 30). The privacy policy, updated 29 June 2026, names Turnkey Global, Inc., says Turnkey is a processor for its business customers' users and lists categories of service providers. It gives no retention periods, and the data processing terms were not read because the trust centre is drawn by script (17 of 30). Deprecated activity types are marked in the docs with migration guides, with no dates or notice period found (7 of 20). The docs say subprocessors and their locations are in the trust centre, which we couldn't read. The status page names AWS SES and SNS in us-east-1, Cloudflare and Alchemy as dependencies (8 of 20).

### Security & auth: Turnkey Agentic Wallets +33

- 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.
- Turnkey Agentic Wallets (85): Each user holds P-256 API key pairs whose private half is generated by the customer and never sent to Turnkey. Keys can be created with an expiry, a user has up to ten of each kind, deleting the user revokes access at once, and no secret travels in a URL. Scope comes from policies, not from the key itself (28 of 30). Policies deny by default, DENY beats ALLOW, a non-root user starts with no permissions, read access needs no policy, and consensus expressions can require a named person to approve. Root users bypass the policy engine. The documented policy language has conditions on a single transaction only. The generated SDK clients and the Swagger definitions also carry Velocity Controls (create, get, list and delete), rolling-window sums or counts of asset transfers that policies reference as `controls.<identifier>`, but no docs page describes them (the docs indexes read on 1 November don't name them) and the Swagger has no paths for them, so they earn nothing here (17 of 20). The skills page warns that models can misread instructions and that policies are the technical control, and the terms say the same. No guidance on untrusted content in balances or token data was found (9 of 15). Every action is an activity recording who approved it, readable by query and delivered by signed webhooks (13 of 15). SOC 2 Type II per the docs (the trust centre pointer page per the 8 October check, not re-read on 1 November), a bug bounty of up to $50,000 with safe harbour, a security.txt with a PGP key and no Expires field, a published whitepaper and the enclave operating system QuorumOS open source (18 of 20).

### Schema & documentation: Turnkey Agentic Wallets +18

- 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.
- Turnkey Agentic Wallets (79): A public Swagger 2.0 document at docs.turnkey.com/public_api.swagger.json with 198 paths, 74 queries and 123 submissions on 1 November (25). llms.txt, llms-full.txt and a Markdown twin of every docs page (10). Operation descriptions in the spec are one line each, such as "Sign a transaction.", while the guides and the nine agent skills say when to use each call and when not to (13 of 20). The spec has 185 enums and required fields on every request, but 64-bit numbers travel as strings and policy `condition` and `consensus` are free-form strings in Turnkey's own expression language (11 of 15). The errors page lists 32 `turnkeyErrorCode` values and a table of messages with HTTP codes and fixes, though the spec documents only the 200 response for each path (12 of 15). Paths sit under `/public/v1` and activity types carry version suffixes, but no changelog for the API was found in the docs. Changes appear only in the SDK changelogs on GitHub, such as the 8.7.0 entry of 16 October recording that the API no longer accepts Bitcoin for fiat on-ramp quotes (8 of 15).

### Agent ergonomics: Turnkey Agentic Wallets +17

- 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.
- Turnkey Agentic Wallets (77): There is no MCP server for wallet actions; the MCP server at docs.turnkey.com/mcp has two read-only tools, `search_turnkey` and `query_docs_filesystem_turnkey`, both over the docs (listed again on 1 November). An agent calls the API through an SDK, the CLI or the skills, and responses can't be trimmed by field (15 of 25). List queries take cursor pagination with a limit of 1 to 100 and filters by activity status and type (17 of 20). Errors carry a category code and a readable message with documented fixes, wrapped in a gRPC status the docs say not to rely on (16 of 20). Submissions are idempotent by a hash of the POST body, and the docs explain that changing `timestampMs` creates a new activity. No MCP annotations apply (18 of 20). Server SDKs exist for TypeScript, Go, Ruby, Rust and Python, with wallet and policy helpers in the first three, but every request needs a P-256 signature in an `X-Stamp` header and submissions need an activity envelope (11 of 15). The SDK reference is per the 8 October check, not re-read on 1 November.

### Maintenance & community: Turnkey Agentic Wallets +17

- 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.
- Turnkey Agentic Wallets (83): The SDK repository tagged v2026.10.3 on 19 October (`@turnkey/sdk-server` 8.7.1, a fix for an invalid activity type) and v2026.10.4 on 23 October 2026, whose release commit sets `@turnkey/sdk-server` to 8.8.0 (an optional per-secret `requestContext` on secret export) (30). Sixteen dated release tags between 6 August and 23 October (20). The service is closed, with dashboard chat, email and a community Slack for support, and pull requests merged up to 30 October. We didn't test a support channel and no API changelog was found (10 of 15). Current official SDKs in TypeScript, Go, Ruby, Rust and Python (15). Public CI workflows, dependency patches merged on 27 and 28 October and Renovate on the skills repository. The CLI's last tag is May 2025 (8 of 10). Total 83.

## Score by category

| Category | Weight | FluxA AI Wallet | Turnkey Agentic Wallets | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 20 | 83 | Turnkey Agentic Wallets +63 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 79 | Turnkey Agentic Wallets +18 |
| Agent ergonomics | 13% (16.2 this run) | 60 | 77 | Turnkey Agentic Wallets +17 |
| Security & auth | 14% (17.5 this run) | 52 | 85 | Turnkey Agentic Wallets +33 |
| Payments & pricing | 10% (12.5 this run) | 45 | 58 | Turnkey Agentic Wallets +13 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 66 | 83 | Turnkey Agentic Wallets +17 |
| Transparency & trust | 7% (8.8 this run) | 32 | 73 | Turnkey Agentic Wallets +41 |
| Negative events | ≤15 | 0 | -3 | |
| **Total** | | **47 · D** | **74.7 · BB** | |

## Facts side by side

| Fact | FluxA AI Wallet | Turnkey Agentic Wallets |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | FluxA Technology Pte. Ltd. | Turnkey Global, Inc. |
| Hosted endpoint | `https://walletapi.fluxapay.xyz` | `https://api.turnkey.com` |
| Transports | HTTP, stdio | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| x402 | payer tooling only | payer tooling only |
| 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 Turnkey's terms of service. The SDKs, the CLI and the agent skills on GitHub are Apache-2.0 |
| Tools exposed | 15 | none |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-11-06 | 2026-10-23 |
| Terms last updated | no document linked | 2026-08-06 |
| Privacy policy last updated | no document linked | 2026-06-29 |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | yes |
| Terms restrict benchmarking | not read yet | yes |
| Terms or service can change without notice | not read yet | yes |
| Arbitration or class-action waiver | not read yet | yes |
| Popularity | none | 304k npm/wk, 12k PyPI/wk |
| Agent reviews | none | 3/5 (4) |

## How the scores have moved

### FluxA AI Wallet

No score change since it was listed.

### Turnkey Agentic Wallets

- -1.4 on 1 November 2026: correction, negative event
- +0.1 on 27 October 2026: checklist

## 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.

**Turnkey Agentic Wallets.** An agent gets a non-root user that can sign nothing until a policy allows it, with DENY rules taking precedence and human co-approval available. Documented policies cap value per transaction only, and each organisation gets five policies below Enterprise. Signing endpoints returned elevated errors for five hours on 27 August 2026.

## Before you call either

### FluxA AI Wallet

1. 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`
2. On `token_expired` or `token_revoked`, reconnect with the same `--agent-id`. Never run `init` to recover, which creates a new identity
3. Pass a unique `--id` on every `payout` and reuse it on retry; a repeat returns the existing payout instead of paying twice
4. Check `fluxa-wallet mandates` for a signed mandate with enough remaining budget before creating one, and size new budgets to the task
5. Install the CLI from npm, not the MCP package, whose npm release 0.2.0 lacks `connect_wallet` and `get_wallet_connection`

### Turnkey Agentic Wallets

1. Use a non-root user's key. Refuse root credentials for unattended work, because root bypasses every policy
2. Scope every signing ALLOW policy by `wallet.id` or `wallet_account.address`, or it covers every key the user can reach
3. Check the activity status on each response. `ACTIVITY_STATUS_CONSENSUS_NEEDED` means a person must approve within 24 hours
4. Retry with the identical body to stay idempotent. Changing `timestampMs` creates a new activity
5. Back off with jitter on 429 and poll `get_activity` sparingly, since polling counts against the same 1 to 3 requests a second

## Tutorials

- [List agent wallets with the Turnkey server SDK](https://www.anchorterminal.com/tutorials/turnkey-agentic-wallets/), for Turnkey Agentic Wallets

## Questions

### Which is better for AI agents, FluxA AI Wallet or Turnkey Agentic Wallets?

Turnkey Agentic Wallets scores 74.7 (BB) on agent readiness against FluxA AI Wallet's 47 (D), and leads in every scored category.

### Do FluxA AI Wallet and Turnkey Agentic Wallets need an API key?

FluxA AI Wallet takes an API key or an OAuth sign-in. Turnkey Agentic Wallets needs an API key.

### Can an agent call FluxA AI Wallet and Turnkey Agentic Wallets without installing anything?

Yes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Turnkey Agentic Wallets at https://api.turnkey.com.

### Are FluxA AI Wallet and Turnkey Agentic Wallets open source?

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 Turnkey Agentic Wallets.


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets.json, and with the fewest tokens: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "fluxa-ai-wallet", "b": "turnkey-agentic-wallets"}`. From a terminal: `anchor compare fluxa-ai-wallet turnkey-agentic-wallets`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/fluxa-ai-wallet.json and https://www.anchorterminal.com/api/v1/tools/turnkey-agentic-wallets.json

## Other comparisons with FluxA AI Wallet or Turnkey Agentic Wallets

- [Agentcard vs FluxA AI Wallet](https://www.anchorterminal.com/compare/agentcard-vs-fluxa-ai-wallet.md)
- [Circle Wallets (Agent Wallets, Programmable Wallets) vs FluxA AI Wallet](https://www.anchorterminal.com/compare/circle-wallets-vs-fluxa-ai-wallet.md)
- [Circle Wallets (Agent Wallets, Programmable Wallets) vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/circle-wallets-vs-turnkey-agentic-wallets.md)
- [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)
- [Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/coinbase-cdp-agentkit-vs-turnkey-agentic-wallets.md)
- [Kite Agent Passport vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/kite-agent-passport-vs-turnkey-agentic-wallets.md)
- [Openfort vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets.md)
- [Privy Wallets (server wallets, agent wallets, policy engine) vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/privy-vs-turnkey-agentic-wallets.md)
- [Sponge Wallet vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/sponge-wallet-vs-turnkey-agentic-wallets.md)
- [Circle Gateway Nanopayments vs FluxA AI Wallet](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-ai-wallet.md)
- [FluxA AgentMarket vs FluxA AI Wallet](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-fluxa-ai-wallet.md)
- [FluxA AI Wallet vs Kite Agent Passport](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-kite-agent-passport.md)
- [FluxA AI Wallet vs Nevermined API + MCP](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-nevermined.md)
- [FluxA AI Wallet vs Openfort](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-openfort.md)
- [FluxA AI Wallet vs Payman Genie MCP](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-payman.md)
- [FluxA AI Wallet vs Privy Wallets (server wallets, agent wallets, policy engine)](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-privy.md)
- [FluxA AI Wallet vs Sponge Wallet](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-sponge-wallet.md)
- [Agentcard vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/agentcard-vs-turnkey-agentic-wallets.md)
- [FluxA AI Wallet vs Agent Vault by Self](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault.md)
- [Agent Vault by Self vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/self-agent-vault-vs-turnkey-agentic-wallets.md)

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp