Head to head · Onchain wallets · October 2026 research run
Openfort vs 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. Both do onchain wallets.
Best agent wallets and spending controls · All 23 wallets comparisons
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
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 this run | Openfort | Turnkey Agentic Wallets | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 88 | 75 | Openfort +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 79 | Openfort +10 |
| Agent ergonomics | 13%16.2 | 65 | 77 | Turnkey Agentic Wallets +12 |
| Security & auth | 14%17.5 | 65 | 85 | Turnkey Agentic Wallets +20 |
| Payments & pricing | 10%12.5 | 60 | 58 | Openfort +2 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 87 | 83 | Openfort +4 |
| Transparency & trust | 7%8.8 | 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
- Call
policies.evaluatewith operationsignEvmTransactionbefore every EVM backend send. The send itself is checked only assignEvmHash - Keep the signing policy and the gas sponsorship policy separate. Linking a signing policy to a fee sponsorship stops it working as a guardrail
- Pass a fee sponsorship on EVM sends. Without one the transaction stays pending with no error
- Give an agent a secret key without
accounts:export, and limit the CLI MCP server to the tools it needs - On a 5xx after a write, read the resource before retrying. On a 429, wait the full
Retry-After
Turnkey Agentic Wallets
- Use a non-root user's key. Refuse root credentials for unattended work, because root bypasses every policy
- Scope every signing ALLOW policy by
wallet.idorwallet_account.address, or it covers every key the user can reach - Check the activity status on each response.
ACTIVITY_STATUS_CONSENSUS_NEEDEDmeans a person must approve within 24 hours - Retry with the identical body to stay idempotent. Changing
timestampMscreates a new activity - Back off with jitter on 429 and poll
get_activitysparingly, 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.
Other comparisons with Openfort or Turnkey Agentic Wallets
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Openfort
- Circle Wallets (Agent Wallets, Programmable Wallets) vs Turnkey Agentic Wallets
- Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Openfort
- Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Turnkey Agentic Wallets
- Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)
- Openfort vs Sponge Wallet
- Privy Wallets (server wallets, agent wallets, policy engine) vs Turnkey Agentic Wallets
- Sponge Wallet vs Turnkey Agentic Wallets
- Agentcard vs Openfort
- Agentcard vs Turnkey Agentic Wallets
Machine-readable
- This page as Markdown
/compare/openfort-vs-turnkey-agentic-wallets.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/openfort.json·/api/v1/tools/turnkey-agentic-wallets.json - From a terminal
anchor compare openfort turnkey-agentic-wallets(the CLI) - Over MCP
compare_tools {"a": "openfort", "b": "turnkey-agentic-wallets"}at/mcp, no key