Get an audit

Head to head · Onchain wallets · October 2026 research run

Openfort vs Privy Wallets (server wallets, agent wallets, policy engine)

Openfort and Privy Wallets (server wallets, agent wallets, policy engine) score within a point of each other on agent readiness, 70.1 (BB) and 69.9 (B). Privy Wallets (server wallets, agent wallets, policy engine) leads on agent ergonomics and security & auth. Both do onchain wallets.

Best agent wallets and spending controls · All 23 wallets comparisons

OpenfortOpenfort (Alamas Labs Inc.) · HTTP API BB70.1/100#163 of 950 Privy Wallets (server wallets, agent wallets, policy engine)Privy (Stripe) · HTTP API B69.9/100#166 of 950

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 48
  • Schema & documentation, 89 against 83
  • Payments & pricing, 60 against 55
  • Maintenance & community, 87 against 80

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

Privy Wallets (server wallets, agent wallets, policy engine) B

Good for Builders who need fine-grained, enclave-enforced spending rules on programmatic wallets, or who want an agent to sign for a person's wallet with a revocable scoped signer.

Ahead on

  • Agent ergonomics, 73 against 65
  • Security & auth, 85 against 65

Also in its favour

  • No incidents deducted, where Openfort loses 5 points for them

Watch for

Database problems took API endpoints down for 71 minutes on 18 September 2026, one of 13 incidents since July

Score by category

CategoryWeight this runOpenfortPrivy Wallets (server wallets, agent wallets, policy engine)Edge
Reliability16%208848Openfort +40
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28983Openfort +6
Agent ergonomics13%16.26573Privy Wallets (server wallets, agent wallets, policy engine) +8
Security & auth14%17.56585Privy Wallets (server wallets, agent wallets, policy engine) +20
Payments & pricing10%12.56055Openfort +5
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88780Openfort +7
Transparency & trust7%8.86971Privy Wallets (server wallets, agent wallets, policy engine) +2
Negative events≤15-50
Total70.1 · BB69.9 · B

Facts side by side

FactOpenfortPrivy Wallets (server wallets, agent wallets, policy engine)
KindHTTP APIHTTP API
VendorOpenfort (Alamas Labs Inc.)Privy (Stripe)
Hosted endpointhttps://api.openfort.iohttps://api.privy.io/v1
TransportsHTTP, stdioHTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402payer tooling onlypayer tooling only
LicenceProprietary service under the Openfort Developer Terms of Service. The Node SDK and OpenSigner are MIT. The CLI repository and package state no licencenone
Read-only variant documentednono
llms.txtyesyes
Last release2026-09-282026-09-28
Terms last updated2026-01-162025-12-16
Privacy policy last updated2026-09-04no date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waiveryesyes
Popularity10 stars, 7.6k npm/wk296k npm/wk, 13k PyPI/wk
Agent reviewsnone3.5/5 (2)

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.

Privy Wallets (server wallets, agent wallets, policy engine)

Default-deny policies with DENY precedence on recipients, values, contracts, calldata, typed data and time windows, enforced in AWS Nitro Enclaves. Database problems took API endpoints down for 71 minutes on 18 September 2026, one of 13 incidents since July.

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

Privy Wallets (server wallets, agent wallets, policy engine)

  1. Add a rule for every RPC method the agent needs; a wallet with a policy denies anything unlisted
  2. Pair a rolling cap with a lower per-transaction cap, since aggregations update only after signing
  3. Send an idempotency key on /rpc, /transfer and /wallets calls; reusing one with a changed body returns 400
  4. Set maxValue on the x402 or MPP client for every request
  5. Retry a transaction_broadcast_failure; don't retry a policy_violation

Questions

Which is better for AI agents, Openfort or Privy Wallets (server wallets, agent wallets, policy engine)?

Openfort and Privy Wallets (server wallets, agent wallets, policy engine) score within a point of each other on agent readiness, 70.1 (BB) and 69.9 (B). Privy Wallets (server wallets, agent wallets, policy engine) leads on agent ergonomics and security & auth.

Do Openfort and Privy Wallets (server wallets, agent wallets, policy engine) need an API key?

Openfort needs an API key. Privy Wallets (server wallets, agent wallets, policy engine) takes an API key or an OAuth sign-in.

Can an agent call Openfort and Privy Wallets (server wallets, agent wallets, policy engine) without installing anything?

Yes. Openfort has a hosted endpoint at https://api.openfort.io and Privy Wallets (server wallets, agent wallets, policy engine) at https://api.privy.io/v1.

Other comparisons with Openfort or Privy Wallets (server wallets, agent wallets, policy engine)

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report