# Openfort vs Turnkey Agentic Wallets

> Turnkey Agentic Wallets scores 76 (BB) to Openfort's 70.1 (BB) for onchain wallets. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets
- Markdown: https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets.md (~2,300 tokens)
- Slim: https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/openfort-vs-turnkey-agentic-wallets.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

Turnkey Agentic Wallets scores 76 (BB) on agent readiness against Openfort's 70.1 (BB), and leads in 3 of 7 scored categories. Openfort leads on reliability and schema & documentation. 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
- Turnkey Agentic Wallets: grade BB, 76/100, rank #39 of 950. 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 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 75
- Schema & documentation, 89 against 79

Also in its favour:
- 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

### 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:
- Agent ergonomics, 77 against 65
- Security & auth, 85 against 65

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

Watch for: Policy conditions cap value per transaction. No daily, rolling or cumulative spending limit was found in the policy language


## Score by category

| Category | Weight | Openfort | Turnkey Agentic Wallets | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 88 | 75 | Openfort +13 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 89 | 79 | Openfort +10 |
| Agent ergonomics | 13% (16.2 this run) | 65 | 77 | Turnkey Agentic Wallets +12 |
| Security & auth | 14% (17.5 this run) | 65 | 85 | Turnkey Agentic Wallets +20 |
| Payments & pricing | 10% (12.5 this run) | 60 | 58 | Openfort +2 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 87 | 83 | Openfort +4 |
| Transparency & trust | 7% (8.8 this run) | 69 | 72 | Turnkey Agentic Wallets +3 |
| Negative events | ≤15 | -5 | 0 | |
| **Total** | | **70.1 · BB** | **76 · BB** | |

## Facts side by side

| Fact | Openfort | Turnkey Agentic Wallets |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Openfort (Alamas Labs Inc.) | Turnkey Global, Inc. |
| Hosted endpoint | `https://api.openfort.io` | `https://api.turnkey.com` |
| Transports | HTTP, stdio | HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| 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 Turnkey's terms of service. The SDKs, the CLI and the agent skills on GitHub are Apache-2.0 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-09-28 | 2026-10-08 |
| Terms last updated | 2026-01-16 | 2026-08-06 |
| Privacy policy last updated | 2026-09-04 | 2026-06-29 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | yes | yes |
| Popularity | 10 stars, 7.6k npm/wk | 304k npm/wk, 12k 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.

**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. Policies cap value per transaction only, with no daily or rolling limit found, and each organisation gets five policies below Enterprise. Signing endpoints returned elevated errors for five hours on 27 August 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`

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

## Questions

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

Turnkey Agentic Wallets scores 76 (BB) on agent readiness against Openfort's 70.1 (BB), and leads in 3 of 7 scored categories. Openfort leads on reliability and schema & documentation.

### Do Openfort and Turnkey Agentic Wallets need an API key?

Both need an API key.

### Can an agent call Openfort and Turnkey Agentic Wallets without installing anything?

Yes. Openfort has a hosted endpoint at https://api.openfort.io and Turnkey Agentic Wallets at https://api.turnkey.com.


## For agents

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

## Other comparisons with Openfort or Turnkey Agentic Wallets

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