# Openfort vs Sponge Wallet

> Openfort scores 70.1 (BB) to Sponge Wallet's 43.2 (E) for onchain wallets. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet
- Markdown: https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet.min.md (~730 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/openfort-vs-sponge-wallet.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-09

Openfort scores 70.1 (BB) on agent readiness against Sponge Wallet's 43.2 (E), and leads in 6 of 7 scored categories. Sponge Wallet leads on payments & pricing. Both do onchain wallets.

- Openfort: grade BB, 70.1/100, rank #163 of 950. Markdown https://www.anchorterminal.com/tools/openfort.md · JSON https://www.anchorterminal.com/api/v1/tools/openfort.json
- Sponge Wallet: grade E, 43.2/100, rank #884 of 950. Markdown https://www.anchorterminal.com/tools/sponge-wallet.md · JSON https://www.anchorterminal.com/api/v1/tools/sponge-wallet.json
- Best agent wallets and spending controls: https://www.anchorterminal.com/best/agent-wallets/index.md
- All 23 wallets comparisons: https://www.anchorterminal.com/compare/agent-wallets/index.md

## Which one, for what

### Openfort (BB)

Good for: A team that wants server-held wallets for agents on EVM chains and Solana with enclave signing, a free start and a CLI an agent can drive.

Ahead on:
- Reliability, 88 against 13
- Schema & documentation, 89 against 66
- Agent ergonomics, 65 against 43
- Security & auth, 65 against 48
- Maintenance & community, 87 against 27
- Transparency & trust, 69 against 39

Also in its favour:
- Agent-ready, a grade of BB or better
- Runs on your own machine

Watch for: An EVM backend send is evaluated only as `signEvmHash`, so address, value and calldata rules do not block it unless the caller pre-flights

### Sponge Wallet (E)

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

Ahead on:
- Payments & pricing, 70 against 60

Also in its favour:
- No incidents deducted, where Openfort loses 5 points for them

Watch for: No status page, SLA or numeric rate limit was found, and the terms say the service may be offered in beta


## Score by category

| Category | Weight | Openfort | Sponge Wallet | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 88 | 13 | Openfort +75 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 66 | Openfort +23 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 43 | Openfort +22 |
| Security & auth | 14% (17.5 this run) | 65 | 48 | Openfort +17 |
| Payments & pricing | 10% (12.5 this run) | 60 | 70 | Sponge Wallet +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 87 | 27 | Openfort +60 |
| Transparency & trust | 7% (8.8 this run) | 69 | 39 | Openfort +30 |
| Negative events | ≤15 | -5 | 0 | |
| **Total** | | **70.1 · BB** | **43.2 · E** | |

## Facts side by side

| Fact | Openfort | Sponge Wallet |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Openfort (Alamas Labs Inc.) | Sponge Inc. |
| Hosted endpoint | `https://api.openfort.io` | `https://api.wallet.paysponge.com` |
| Transports | HTTP, stdio | HTTP |
| Auth | API key | OAuth or key |
| Pricing | Freemium | Free |
| x402 | payer tooling only | payer tooling only |
| Licence | Proprietary service under the Openfort Developer Terms of Service. The Node SDK and OpenSigner are MIT. The CLI repository and package state no licence | Proprietary service under Sponge's terms of service. The SDK and CLI packages on npm are MIT, and the repository they name is private |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-28 | 2026-07-07 |
| Terms last updated | 2026-01-16 | 2026-06-30 |
| Privacy policy last updated | 2026-09-04 | 2026-06-30 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 10 stars, 7.6k npm/wk | 126 npm/wk, 20 PyPI/wk |

## Verdicts

**Openfort.** Backend wallets sign inside a GCP Confidential Space enclave, secret keys carry 26 scopes, and rate limits, errors and prices are published. On EVM, a backend send reaches the policy engine only as a hash, so address and value rules bind only when the caller runs the pre-flight check first.

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

## Before you call either

### Openfort

1. Call `policies.evaluate` with operation `signEvmTransaction` before every EVM backend send. The send itself is checked only as `signEvmHash`
2. Keep the signing policy and the gas sponsorship policy separate. Linking a signing policy to a fee sponsorship stops it working as a guardrail
3. Pass a fee sponsorship on EVM sends. Without one the transaction stays pending with no error
4. Give an agent a secret key without `accounts:export`, and limit the CLI MCP server to the tools it needs
5. On a 5xx after a write, read the resource before retrying. On a 429, wait the full `Retry-After`

### Sponge Wallet

1. Send `Sponge-Version` on every REST request. The skill file marks it required and the API answers with version status headers
2. Use `evmTransfer` and `solanaTransfer`, the helpers the docs describe as enforcing allowlists and spending limits, not plain `transfer`
3. Store the `apiKey` from registration at once. It is returned a single time, and losing it means registering again
4. Call `GET /api/discover/{serviceId}` before `POST /api/paid/fetch`. The skill file says direct service URLs fail with auth errors
5. Treat `card details` output as secret. It returns an encrypted card number and CVC with a one-time `secret_key`

## Questions

### Which is better for AI agents, Openfort or Sponge Wallet?

Openfort scores 70.1 (BB) on agent readiness against Sponge Wallet's 43.2 (E), and leads in 6 of 7 scored categories. Sponge Wallet leads on payments & pricing.

### Do Openfort and Sponge Wallet need an API key?

Openfort needs an API key. Sponge Wallet takes an API key or an OAuth sign-in.

### Can an agent call Openfort and Sponge Wallet without installing anything?

Yes. Openfort has a hosted endpoint at https://api.openfort.io and Sponge Wallet at https://api.wallet.paysponge.com.


## For agents

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

## Other comparisons with Openfort or Sponge Wallet

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