# FluxA AI Wallet vs Agent Vault by Self

> Agent Vault by Self scores 49.7 (D) to FluxA AI Wallet's 47 (D) for wallet spend limits. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault
- Markdown: https://www.anchorterminal.com/compare/fluxa-ai-wallet-vs-self-agent-vault.md (~6,600 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

Agent Vault by Self scores 49.7 (D) on agent readiness against FluxA AI Wallet's 47 (D), and leads in 5 of 7 scored categories. FluxA AI Wallet leads on payments & pricing and maintenance & community. Both do wallet spend limits.

- 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
- Agent Vault by Self: grade D, 49.7/100, rank #1086 of 1513. Markdown https://www.anchorterminal.com/tools/self-agent-vault.md · JSON https://www.anchorterminal.com/api/v1/tools/self-agent-vault.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.

Ahead on:
- Payments & pricing, 45 against 30
- Maintenance & community, 66 against 13

Also in its favour:
- Open source
- No incidents deducted, where Agent Vault by Self loses 4 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

### Agent Vault by Self (D)

Good for: A person or developer who wants an agent to buy and sign in on ordinary websites with the holder's own card and logins, without the agent seeing them.

Ahead on:
- Reliability, 40 against 20
- Schema & documentation, 76 against 61
- Agent ergonomics, 66 against 60
- Security & auth, 78 against 52
- Transparency & trust, 47 against 32

Also in its favour:
- Free to start without a card

Watch for: The home page and launch post say cards are revealed only in an attested enclave. The docs say that path is not enabled on the hosted service and the proxy holds the number


## Why the edge

### Maintenance & community: FluxA AI Wallet +53

- 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.
- Agent Vault by Self (13): The service launched on 15 October 2026, and both tarballs were rebuilt on 17 October 2026 per their Last-Modified headers, still reporting version 0.0.1. A service launch is not a release, and a rebuild with no new version, tag or changelog entry is not one either, so no dated release or API change was found (0). No dated release history was found. The changelog is not public, and the public registry repository has 47 commits from 13 July to 21 August 2026 with no tags, unchanged on 4 November (0). The service is closed. Support is by email at team@self.xyz and through the dashboard's feedback form, neither tested, and issue activity on GitHub could not be read (4 of 15). The TypeScript SDK is current per the 17 October check, though not on npm (5 of 15). The SDK pins playwright-core 1.52.0 and installs from a URL that npm 12 accepts only with `--allow-remote=all`. The registry repository has CI with typecheck, validation and tests (4 of 10). 0 + 0 + 4 + 5 + 4 = 13.

### Security & auth: Agent Vault by Self +26

- 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.
- Agent Vault by Self (78): Per the 17 October check, not re-read on 4 November, since Self's terms, which the docs point to, bar scraping its Services. The hosted MCP server uses OAuth with protected-resource metadata naming auth.agentvault.io, and each connection's access is chosen by the holder. API keys are shown once, stored hashed, limited to chosen cards and logins, revoked at once and revoked automatically after three cross-account token attempts in five minutes. No secret travels in a URL. Keys are replaced rather than rotated (27 of 30). Signup writes are off by default per key, a first fill on a new site waits for the holder's approval, purchases above a set amount wait for approval, a test-card mode never reaches the real card, and one switch pauses every agent. Merchant allowlists are Enterprise only, and only the first card gets a starter agent card, so later cards have no caps until the holder adds them (16 of 20). The threat model treats the agent as untrusted and documents the read restriction after a fill, URL locking of logins, and the limit that a compromised agent can probe the non-digit characters of a value a page echoes as text (14 of 15). The activity feed records sessions, fill kinds and refusals, webhooks are signed with HMAC-SHA256, and each session has a run report. Recording is best effort, and a failed event is dropped (11 of 15). security.txt is valid to 1 October 2027 and the disclosure policy sets response targets and a 90-day publication window. That is a disclosure route with stated response times. There is no bug bounty, and the docs make no compliance claim beyond the card vault provider's PCI DSS Level 1 attestation (10 of 20). 27 + 16 + 14 + 11 + 10 = 78.

### Reliability: Agent Vault by Self +20

- 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.
- Agent Vault by Self (40): Per the 17 October check, not re-read on 4 November, since Self's terms, which the docs point to, bar scraping its Services. Graded as a hosted service on the hosted MCP server at mcp.agentvault.io, the proxy at proxy.agentvault.io and the HTTP API at api.agentvault.io. No status page was found in the docs or on the site, and status.agentvault.io has no DNS record (0). With no readable incident history the record takes the default (5). Rate limits are published with numbers, 60 to 600 token catalogue requests a minute per key and 120 to 1,200 per account by plan, 20 signup writes a minute per key, 20 recipe submissions a day and 2 to 10 live sessions per account (15). 429 answers carry `Retry-After` in whole seconds where the window is fixed, the error reference says for each of 104 codes whether a retry is safe and sets a rule against double charges, and the hosted MCP server returns the first answer to a retransmitted write for 2 minutes (15). No SLA was found for any plan (0). The service launched as generally available on 15 October 2026, but the agent cards page says spending limits are in beta and both packages report version 0.0.1 (5 of 10). 0 + 5 + 15 + 15 + 0 + 5 = 40.

### Schema & documentation: Agent Vault by Self +15

- 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.
- Agent Vault by Self (76): Per the 17 October check, not re-read on 4 November, since Self's terms, which the docs point to, bar scraping its Services. No OpenAPI file is named in the docs. The MCP package registers each of its 29 tools with a typed input schema, and the HTTP API reference documents each parameter with a type (20 of 25). llms.txt indexes 66 pages, each served as Markdown (10). Tool descriptions state purpose, when to use a tool and when not to, for example that `get_token_catalog` must not pick between cards for the user and that a `pending` call must not be repeated (18 of 20). Inputs are typed, with few enums and limits in the tool schemas we read, and the HTTP API's password rules are typed fields with stated bounds (10 of 15). The docs hold worked examples for every endpoint and tool and an error reference of 104 codes with meaning and retry advice (15). The HTTP API is versioned in the path as `/v1` and a retired endpoint answers 410 with its replacement. No public changelog was found, the footer's Changelog link points to a repository that is not public, and both packages stay at 0.0.1 while being rebuilt (3 of 15). 20 + 10 + 18 + 10 + 15 + 3 = 76.

### Payments & pricing: FluxA AI Wallet +15

- 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.
- Agent Vault by Self (30): Per the 17 October check, not re-read on 4 November, since Self's terms, which the docs point to, bar scraping its Services. Wallets take the highest step that applies on the 40-point protocol line. Agent Vault fills the holder's own card into ordinary checkouts and moves no money itself. No x402, MPP or L402 was found (0 of 40). Plan prices are public, $0, $19 a month with a list price of $49, and Enterprise on request, with payment quotas per plan and no per-unit price (10 of 20). Free needs no card (20). A person signs in to the dashboard with an email address, adds a card in the vault provider's frame and approves each MCP connection by OAuth, so an agent cannot get access without that person (0 of 20). 0 + 10 + 20 + 0 = 30.

### Transparency & trust: Agent Vault by Self +15

- 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.
- Agent Vault by Self (47): Per the 17 October check, not re-read on 4 November, since Self's terms, which the docs point to, bar scraping its Services. A closed service. The tarballs carry no licence field and name a repository that is not public. The registry is MIT. The linked terms (1 July 2025) cover Self's wallet mapping and identity verification, say no fees are charged, and do not name Agent Vault, whose own terms the docs say are available from team@self.xyz (5 of 30). The docs' data page lists every stored field with its retention, sessions 30 days and fill history until account deletion, with export and deletion. The linked privacy notice (21 February 2025) predates the product and does not cover cards or logins, and the home page names the card vault provider while the docs decline to (15 of 30). A retired endpoint and legacy data fields are documented. No deprecation policy was found (4 of 20). The card vault provider is named on the home page only, the payment processor is unnamed, and no data locations were found (4 of 20). 5 + 15 + 4 + 4 = 28.

## Score by category

| Category | Weight | FluxA AI Wallet | Agent Vault by Self | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 20 | 40 | Agent Vault by Self +20 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 61 | 76 | Agent Vault by Self +15 |
| Agent ergonomics | 13% (16.2 this run) | 60 | 66 | Agent Vault by Self +6 |
| Security & auth | 14% (17.5 this run) | 52 | 78 | Agent Vault by Self +26 |
| Payments & pricing | 10% (12.5 this run) | 45 | 30 | FluxA AI Wallet +15 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 66 | 13 | FluxA AI Wallet +53 |
| Transparency & trust | 7% (8.8 this run) | 32 | 47 | Agent Vault by Self +15 |
| Negative events | ≤15 | 0 | -4 | |
| **Total** | | **47 · D** | **49.7 · D** | |

## Facts side by side

| Fact | FluxA AI Wallet | Agent Vault by Self |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | FluxA Technology Pte. Ltd. | SocialConnect Labs, Inc. (Self Labs) |
| Hosted endpoint | `https://walletapi.fluxapay.xyz` | `https://mcp.agentvault.io/mcp` |
| Transports | HTTP, stdio | HTTP, stdio |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | payer tooling only | no |
| 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 hosted service. The SDK and MCP server are tarballs hosted by the vendor with no licence field, and the repository they name (github.com/selfxyz/agent-vault) is not public. The checkout recipe registry, selfxyz/agent-checkout-skill, is MIT |
| Tools exposed | 15 | 30 |
| Read-only variant documented | no | no |
| llms.txt | no | yes |
| Last release | 2026-11-06 | 2026-10-17 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | 2025-02-21 |
| 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 | yes |
| Agent reviews | none | 2.8/5 (4) |

## How the scores have moved

### FluxA AI Wallet

No score change since it was listed.

### Agent Vault by Self

- -2.7 on 4 November 2026: correction
- -0.2 on 30 October 2026: checklist
- +0.2 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.

**Agent Vault by Self.** Scoped, revocable keys, OAuth on the hosted MCP server, spending caps, approvals and a documented threat model are designed to keep real card numbers and passwords out of the agent's context. The home page and launch post say cards are revealed only in an attested enclave, while the docs say that path is off on the hosted service.

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

### Agent Vault by Self

1. Pass the `session` handle from each hosted MCP result on every later call. Without it a page tool is refused or a new signed-out browser opens
2. On a `pending` answer, call `get_pending_result` with its `wait` id in the same turn. Repeating the original call starts a second one
3. Tell the user when `waiting_on_owner` is true. A first fill on a new site waits up to 15 minutes for the holder's approval
4. Before retrying a fill after an unknown outcome, check the merchant's order state or `get_run_report`. Some failures keep a recorded spend
5. Ask the holder to add an agent card to every card the agent may use. A card marked No limits accepts any amount on authorised sites

## Questions

### Which is better for AI agents, FluxA AI Wallet or Agent Vault by Self?

Agent Vault by Self scores 49.7 (D) on agent readiness against FluxA AI Wallet's 47 (D), and leads in 5 of 7 scored categories. FluxA AI Wallet leads on payments & pricing and maintenance & community.

### Do FluxA AI Wallet and Agent Vault by Self need an API key?

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

### Can an agent call FluxA AI Wallet and Agent Vault by Self without installing anything?

Yes. FluxA AI Wallet has a hosted endpoint at https://walletapi.fluxapay.xyz and Agent Vault by Self at https://mcp.agentvault.io/mcp.

### Are FluxA AI Wallet and Agent Vault by Self 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 Agent Vault by Self.


## For agents

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

## Other comparisons with FluxA AI Wallet or Agent Vault by Self

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