sak-agentwallet-adapter
v1.0.1
Published
Non-custodial wallet adapter for Solana Agent Kit — wraps agentwallet-sdk's Solana keypair to match SAK's wallet interface
Downloads
246
Maintainers
Readme
sak-agentwallet-adapter
Drop-in non-custodial wallet adapter for Solana Agent Kit. The agent holds its own keypair — no Privy account, no Turnkey API key, no vendor dependency.
Why?
Solana Agent Kit currently supports Privy and Turnkey for wallet integration. Both are solid products, but they're embedded/custodial — a third party controls or co-manages the key.
This adapter plugs agentwallet-sdk's keypair-based Solana wallet into SAK's wallet interface. Your agent signs its own transactions locally. The key never leaves the process.
Install
npm install sak-agentwallet-adapter agentwallet-sdk @solana/web3.jsQuick start
import { AgentWalletSAKAdapter } from 'sak-agentwallet-adapter';
import { SolanaAgentKit } from 'solana-agent-kit';
// Agent generates or loads its own keypair
const wallet = new AgentWalletSAKAdapter({
privateKeyBase58: 'your-base58-private-key',
rpcUrl: 'https://api.mainnet-beta.solana.com',
});
// Plug into SAK — all 60+ SAK actions just work
const agent = new SolanaAgentKit(wallet, {
// your SAK config
});
// The agent can now trade, transfer, stake, etc.
// but the private key stays local. No vendor. No API calls to sign.What you get
- Non-custodial: Agent holds the keypair. Period.
- Full SAK compatibility:
signTransaction,signAllTransactions,connection— the standard interface SAK expects. - Works with agentwallet-sdk v3: Same keypair can also do Jupiter swaps, x402 micropayments, and CCTP cross-chain bridging through the full SDK.
How it works
The adapter takes a base58 private key, constructs a Keypair, and implements SAK's wallet interface. When SAK calls signTransaction, the adapter signs locally using the keypair. That's it — no network calls, no vendor APIs, no magic.
When to use this vs Privy/Turnkey
| | sak-agentwallet-adapter | Privy/Turnkey | |---|---|---| | Key custody | Agent holds key locally | Vendor manages/co-manages | | Vendor dependency | None | Requires active API account | | Setup | One keypair, one RPC URL | OAuth config, API keys, dashboard setup | | Best for | Autonomous agents, self-hosted bots | User-facing apps, teams that want managed infra |
If your agent runs autonomously and you want it to truly own its wallet — use this.
If you're building a consumer app and want managed auth flows — Privy/Turnkey are great choices.
License
MIT
