# FluxA AI Wallet vs Nevermined API + MCP

> Nevermined scores 71.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-nevermined
- Markdown: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-nevermined.md (~7,900 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

Nevermined API + MCP scores 71.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
- Nevermined API + MCP: grade BB, 71.7/100, rank #150 of 1513. Markdown https://www.anchorterminal.com/tools/nevermined.md · JSON https://www.anchorterminal.com/api/v1/tools/nevermined.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
- Best payment and monetisation platforms for AI agents: https://www.anchorterminal.com/best/payment-platforms/index.md
- All 104 platforms comparisons: https://www.anchorterminal.com/compare/payment-platforms/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

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

### Nevermined API + MCP (BB)

Good for: An agent or AI assistant that needs to find and pay per-call x402 or MPP services under a spending cap a person approves, and for builders who want to charge agents by plan or credit with card or stablecoin settlement.

Ahead on:
- Reliability, 63 against 20
- Schema & documentation, 85 against 61
- Agent ergonomics, 76 against 60
- Security & auth, 74 against 52
- Payments & pricing, 70 against 45
- Maintenance & community, 81 against 66
- Transparency & trust, 70 against 32

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

Watch for: A person creates the first account in a browser, and every paid route needs a person to approve a key, consent or Delegation


## Why the edge

### Reliability: Nevermined API + MCP +43

- 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.
- Nevermined API + MCP (63): Hosted lines, graded on the Catalog MCP server (which carries the Router's route_by_intent, quote_service and pay_service) and the REST API, the surfaces both graders used. status.nevermined.ai is an Upptime page built from the public nevermined-io/uptime repository, with history for five root URLs (website, app, docs, and the sandbox and live API roots). It doesn't monitor mcp.live.nevermined.app or any Router route. At 16:50 UTC on 17 October 2026 the repository's newest commit was the daily summary of 6 October, and its daily response-time records stop on 5 September, so the page had recorded nothing for 11 days. Snipcart earned 15 for an Upptime page that checks root URLs and is still running, and Brave's page earned 10 with its components unmonitored (10 of 20). The record from 28 July (when the API monitors started) to 6 October shows both APIs clean and one docs outage, 502s from 20:09 UTC on 2 September to 05:39 UTC on 3 September, about 9.5 hours. The docs aren't a surface an agent calls, so minor incidents only (20). The Router documents per-key, per-slug and IP-keyed global 429 buckets without request-rate numbers, plus a default of 10 concurrent routed requests per user and about 60 device-flow polls a minute per IP. Paid earned 7 for limits described without numbers, and the published figures add 1 (8 of 15). 429s carry Retry-After, the global bucket adds Retry-After-short, Retry-After-long and RateLimit headers, every error carries a retryable flag, and payments take a requestId, with documented handling of indeterminate and duplicate payments (15). No SLA in the terms or on the pricing page (0). The Catalog MCP and the Router carry no beta or preview label (10).

### Transparency & trust: Nevermined API + MCP +38

- 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.
- Nevermined API + MCP (70): The editorial half. The SDKs are Apache-2.0, while the platform, API and MCP server are closed (the registry names a private repository, nevermined-io/nvm-monorepo). The terms at nevermined.ai/legal/terms are published but undated, are written for a wallet-connected app that 'does not transfer any Crypto Assets', don't mention cards, Delegations, the Router or the Subscription, and let Nevermined end the agreement without notice. Paid earned 17 for a closed platform under an undated agreement with open SDKs (17 of 30). The Data Policy on nevermined.app gives retention by category (account and transaction records ten years, audit logs five, usage data 24 months, analytics 12 months, masked session recordings 30 days, paid call responses 24 hours), which agrees with the MCP tools' 24-hour result window, and says stored responses aren't used for training. The older policy the nevermined.ai footer links is a generic notice for the marketing site, naming visitor identification partners (retention.com, RB2B), and the Data Policy says that site has its own notice, so the two don't conflict on the platform. The Data Policy is undated (24 of 30). The versioning page is a deprecation policy, with the 1.0 floor supported indefinitely, no forced sunsets and breaking changes gated behind pins, and the SDK changelogs carry dated deprecations such as the `environment` option. The Router refuses legacy API keys (403 BCK.ROUTER.0008) with no date or notice found (16 of 20). Annex B lists seven sub-processors with locations and transfer mechanisms and promises 60 days' notice of changes, hosting is in the EU or Switzerland, and product analytics run on PostHog's EU instance with a documented opt-out. The cloud host and compliance platform aren't named, and Privy (sign-in) and Braintree (cards), which the auth manifest and docs name, aren't listed (14 of 20). The provenance half is computed from the provenance block.

### Payments & pricing: Nevermined API + MCP +25

- 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.
- Nevermined API + MCP (70): Payment platforms take the highest step that applies on the 40-point protocol line (40 on all their own endpoints, 30 on part of their own API, 25 when their merchants can accept one, 20 for a facilitator, 15 for paying as a buyer, 0 for only a protocol of their own). Nevermined's own API and MCP server take a key or OAuth credential, not a 402. Its merchants answer 402 over x402 and MPP through Nevermined's middleware and facilitator, in Nevermined's own schemes (`nvm:erc4337`, `nvm:card-delegation` and the MPP method `nevermined`), which settle against a Nevermined plan, so a stock x402 or MPP client can't pay them. ATXP and Circle earned the merchant step with their own middleware and facilitator, and the Stripe MCP dossier read Stripe's own card method under MPP the same way. The line could also be read as the own-protocol step, so we say which reading we took. The Router also pays standard x402 on Base and MPP on Tempo as a buyer (25 of 40). Fees public without a login, 1 per cent on stablecoin and 2 per cent on card settlement for merchants, 2 per cent on top for external services through the Router, and a USD 20 monthly Subscription for 20,000 credits at published per-endpoint rates (20). The Free plan is $0 with no card requirement found, and sandbox runs on testnet funds with two free test merchants (20). Three discovery tools (list_categories, search_services, get_service) answer with no credential, while quoting, picking, paying and the ledger need an account a person creates in a browser, and the OAuth and device flows need a person's approval. Both graders read the keyless discovery as 5, a judgement call (5 of 20).

### Schema & documentation: Nevermined API + MCP +24

- 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.
- Nevermined API + MCP (85): Every one of the 12 Catalog MCP tools has a typed JSON Schema input (tools/list read without a credential on 17 October 2026). llms.txt links three public OpenAPI files, openapi.json (OpenAPI 3.1, 39 paths including 11 Router routes), oauth-openapi.json (12 paths) and organizations-openapi.json (65 paths). `POST /router/select`, the REST side of route_by_intent, and the `/api/v1/mpp/challenge` and `/api/v1/mpp/settle` routes in the MPP seller guide aren't in any of them. The catalogue's REST reads answer 403 to outside callers by design, so they aren't counted. Missing routes cost 3, as for Presidio and ComplyCube (22 of 25). llms.txt with a Markdown twin of every page, and a Docs MCP server (10). The descriptions state purpose and when to use each tool instead of its neighbour, such as route_by_intent 'instead of search_services when you want the right service for a task', and when not to, such as autoPay suiting only single-endpoint services. They are long, which ergonomics counts (18 of 20). Enums on `protocol` and `funding`, bounds on `pageSize`, `limit` and `maxTotalCents`, a uuid format on `paymentId` and `additionalProperties: false`, but `body` has no type, `headers` is a free string map, `method` a free string and `from` and `to` plain strings with no date format. Paid earned 12 for enums and required flags beside free-form maps, and an untyped body sits below that (11 of 15). Each tool page has request and response examples and a refusals table, and the API error model documents a stable `BCK.*` code, message, hint and retryable flag, with a full code list (15). The API is versioned by MAJOR.MINOR with a `Nevermined-Version` header, per-key pins and a written compatibility policy. The SDKs keep dated CHANGELOG files and there's a dated product update of 15 October 2026, but no changelog for the platform, API or MCP server was found. Paid earned 7 for versioning with no API changelog, and the SDK changelogs add 2 (9 of 15).

### Security & auth: Nevermined API + MCP +22

- 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.
- Nevermined API + MCP (74): Plain API keys are bearer credentials per environment, accepted only in the Authorization header (the auth manifest rules out a query parameter), with Admin and member roles and no scopes found, and an admin key can move organisation funds. MCP hosts can use OAuth 2.1 with PKCE and the commerce scope, whose short-lived credential spends only from the Delegation a person approved, with one-time refresh tokens and revocation at `/oauth/revoke`. The device flow mints a key for one agent's plan. OpenRouter earned 25 for bearer keys and OAuth PKCE with no permission scopes, the same kind of model (25 of 30). Delegations carry a hard cap, transaction count and expiry, are revocable and are never widened or extended in place. An agent can't set its own cap, since setup_delegation hands a person one URL, and Visa delegations need a passkey. Recipient scope is optional and unset means any merchant, there's no read-only key, and nothing asks before a paid call within the cap. Composio earned 16 with read-only filters and optional approvals, and here caps a person sets stand in for the missing read-only mode (16 of 20). pay_service relays merchant responses unchanged. Listing text is sanitised and moderated, route_by_intent ranks without a model reading listings and get_service marks `docs` examples as unverified provider documentation, but no guidance on treating merchant responses as untrusted was found (6 of 15). Per-payment records with delivery status in list_payments, an organisation activity feed (`GET /organizations/{orgId}/activity`), an `x-correlation-id` on every response, connected agents that can be listed and revoked, and audit logs of actions under Agentic Tokens kept five years per the Data Policy. Unpaid tool calls leave no record the operator can read (14 of 15). security.txt is valid on nevermined.app (security@nevermined.io, expires 2 May 2027) and missing on nevermined.ai. The certifications page and pricing page claim SOC 2 Type II, ISO/IEC 27001:2022 and PCI SAQ-D, while the Data Policy's section 8.5 calls the ISO 27001 programme in progress with Stage 2 scheduled. The Trust Center renders only with JavaScript and wasn't read, no bug bounty was found, and GitHub advisories couldn't be read because GitHub's API refused us. Composio earned 12 for SOC 2 Type II and private reporting without security.txt (13 of 20).

### Agent ergonomics: Nevermined API + MCP +16

- 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.
- Nevermined API + MCP (76): Graded on the Catalog MCP server, with the REST API where a line covers it. Twelve tools put it in the 11 to 30 band, with no toolsets or read-only subsets. The definitions come to about 41,000 characters (pay_service alone about 9,800), and the band is read without a size deduction, as openmetadata (16 tools, 49,602 characters) and plane (30 tools, about 67,000) were (15 of 25). search_services takes `pageSize` 1 to 100 but returns only the first page, since its `pageToken` can't be passed back, route_by_intent's shortlist takes `limit` 1 to 20, and list_payments filters by Delegation and date and stops at 1,000 records with no cursor (14 of 20). Refusals come back as JSON with `error`, `code`, `retryable` and `instructions`, often naming the next tool, such as `no_delegation` pointing to setup_delegation (20). A repeated paid call with the same `requestId` is answered from the stored result for 24 hours, and `payment_indeterminate` and `already_paid` are documented. None of the 12 tools carries readOnlyHint or destructiveHint, though each declares a `securitySchemes` entry (`noauth`, or `oauth2` with the commerce scope). Composio earned 15 with annotations and no idempotency keys, so the reverse case takes 12 (12 of 20). Most tools need one argument or none, autoPay defaults to off, and official SDKs ship in TypeScript and Python (15).

## Score by category

| Category | Weight | FluxA AI Wallet | Nevermined API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 20 | 63 | Nevermined API + MCP +43 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 85 | Nevermined API + MCP +24 |
| Agent ergonomics | 13% (16.2 this run) | 60 | 76 | Nevermined API + MCP +16 |
| Security & auth | 14% (17.5 this run) | 52 | 74 | Nevermined API + MCP +22 |
| Payments & pricing | 10% (12.5 this run) | 45 | 70 | Nevermined API + MCP +25 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 66 | 81 | Nevermined API + MCP +15 |
| Transparency & trust | 7% (8.8 this run) | 32 | 70 | Nevermined API + MCP +38 |
| Negative events | ≤15 | 0 | -2 | |
| **Total** | | **47 · D** | **71.7 · BB** | |

## Facts side by side

| Fact | FluxA AI Wallet | Nevermined API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | FluxA Technology Pte. Ltd. | Nevermined |
| Hosted endpoint | `https://walletapi.fluxapay.xyz` | `https://api.live.nevermined.app` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or 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 | Apache-2.0 |
| Tools exposed | 15 | 12 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| MCP registry | not listed | `io.github.nevermined-io/catalog` |
| Last release | 2026-11-06 | 2026-09-29 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| 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 | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 17 stars, 468 npm/wk, 4.4k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

## How the scores have moved

### FluxA AI Wallet

No score change since it was listed.

### Nevermined API + MCP

- +0.2 on 27 October 2026: checklist
- +0.7 on 17 October 2026: reliability, new evidence, correction, negative event
- -0.3 on 8 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.

**Nevermined API + MCP.** Delegations cap what an agent can spend by amount, count and expiry, and the Catalog MCP's 12 typed tools make idempotent payments and return refusals naming the next step. Every paid route needs a person to approve a key or budget, the tools carry no read-only or destructive annotations, and the status page monitors no MCP or Router route.

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

### Nevermined API + MCP

1. Rehearse on https://mcp.sandbox.nevermined.app/mcp with testnet funds. On live, pay_service and route_by_intent with autoPay move real money
2. Call get_service before pay_service and pass the endpoint's payServiceArgs, since a bare slug on a multi-endpoint service answers 404 instead of a payment
3. Keep one requestId per purchase across retries. On payment_indeterminate, check list_payments before retrying, and never retry with a new requestId
4. Set maxTotalCents on paid calls, since the Router's 2 per cent fee on external services comes out of the same Delegation cap
5. On no_delegation, call setup_delegation and pass its URL to the account owner. You can't set the cap yourself

## Questions

### Which is better for AI agents, FluxA AI Wallet or Nevermined API + MCP?

Nevermined API + MCP scores 71.7 (BB) on agent readiness against FluxA AI Wallet's 47 (D), and leads in every scored category.

### Do FluxA AI Wallet and Nevermined API + MCP need an API key?

Both take an API key or an OAuth sign-in.

### Can an agent call FluxA AI Wallet and Nevermined API + MCP without installing anything?

Yes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Nevermined API + MCP at https://api.live.nevermined.app.

### Are FluxA AI Wallet and Nevermined API + MCP 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 Nevermined API + MCP.


## For agents

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

## Other comparisons with FluxA AI Wallet or Nevermined API + MCP

- [Lago vs Nevermined API + MCP](https://www.anchorterminal.com/compare/lago-vs-nevermined.md)
- [Metronome vs Nevermined API + MCP](https://www.anchorterminal.com/compare/metronome-vs-nevermined.md)
- [Nevermined API + MCP vs Orb](https://www.anchorterminal.com/compare/nevermined-vs-orb.md)
- [Nevermined API + MCP vs Paid](https://www.anchorterminal.com/compare/nevermined-vs-paid.md)
- [Agentcard vs FluxA AI Wallet](https://www.anchorterminal.com/compare/agentcard-vs-fluxa-ai-wallet.md)
- [Crossmint API + Docs MCP vs Nevermined API + MCP](https://www.anchorterminal.com/compare/crossmint-vs-nevermined.md)
- [ATXP vs Nevermined API + MCP](https://www.anchorterminal.com/compare/atxp-vs-nevermined.md)
- [Nevermined API + MCP vs Skyfire API + MCP](https://www.anchorterminal.com/compare/nevermined-vs-skyfire.md)
- [Nevermined API + MCP vs Tempo](https://www.anchorterminal.com/compare/nevermined-vs-tempo.md)
- [Nevermined API + MCP vs TermiX AACP](https://www.anchorterminal.com/compare/nevermined-vs-termix.md)
- [Circle Wallets (Agent Wallets, Programmable Wallets) vs FluxA AI Wallet](https://www.anchorterminal.com/compare/circle-wallets-vs-fluxa-ai-wallet.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)
- [Circle Gateway Nanopayments vs FluxA AI Wallet](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-fluxa-ai-wallet.md)
- [Circle Gateway Nanopayments vs Nevermined API + MCP](https://www.anchorterminal.com/compare/circle-gateway-nanopayments-vs-nevermined.md)
- [FluxA AgentMarket vs FluxA AI Wallet](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-fluxa-ai-wallet.md)
- [FluxA AgentMarket vs Nevermined API + MCP](https://www.anchorterminal.com/compare/fluxa-agentmarket-vs-nevermined.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 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)
- [FluxA AI Wallet vs Turnkey Agentic Wallets](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-turnkey-agentic-wallets.md)
- [Nevermined API + MCP vs Payman Genie MCP](https://www.anchorterminal.com/compare/nevermined-vs-payman.md)
- [Nevermined API + MCP vs Stripe API + MCP](https://www.anchorterminal.com/compare/nevermined-vs-stripe-mcp.md)
- [Adyen MCP server vs Nevermined API + MCP](https://www.anchorterminal.com/compare/adyen-mcp-server-vs-nevermined.md)
- [Nevermined API + MCP vs PayPal MCP server](https://www.anchorterminal.com/compare/nevermined-vs-paypal-mcp-server.md)
- [FluxA AI Wallet vs Agent Vault by Self](https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault.md)

## Disclosure

- Nevermined's Router competes with letme, which Anchor Terminal's founder builds. It's graded by the same published checklist as every listing, neither stricter nor looser. Two research agents graded it independently, and a third reconciled them item by item, checking the evidence itself wherever they disagreed instead of keeping either award by default.

---

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