Crank vs Coinbase AgentKit¶
The main difference is where the key lives. Coinbase AgentKit's flagship wallet option is Agentic Wallets (generally available since February 2026): keys are generated and used inside Coinbase's Trusted Execution Environment (TEE) — isolated infrastructure Coinbase operates — and an encrypted copy is stored in Coinbase's database. Crank's wallets stay with the owner: value-bearing tools return an unsigned transaction, and the owner's own key — never generated or held by Crank — signs it; for unattended operation, scoped session credentials run on TEE-isolated signing infrastructure without the platform ever holding a wallet. Both platforms enforce guardrails; they enforce different kinds, at different points relative to the key: Coinbase's policy engine governs payments (allowances, session caps, allowlists) on its managed wallets, while Crank's governs trading risk (position and drawdown limits, kill switch with unwind) on a wallet the owner controls.
Comparison¶
| Dimension | Crank | Coinbase AgentKit |
|---|---|---|
| Custody location | The wallet owner's own wallet. Crank never generates, holds, or has access to a private key. Scoped session credentials for unattended operation run on TEE-isolated signing infrastructure and are revocable at any time. | Agentic Wallets (GA February 2026): private keys are generated and used inside AWS Nitro Enclaves (Coinbase's TEE) — not visible to Coinbase or AWS during use. An encrypted copy is stored in Coinbase's database, decryptable only with the developer's Wallet Secret. AgentKit also supports developer-controlled wallets (for example via Viem) as an alternative. |
| Server-enforced guardrails | A trading-risk policy (max trade size, daily limit, token allowlist/banlist, position limit, drawdown limit, kill switch with automated position unwind) is enforced server-side on a wallet the owner controls directly. Refused actions are never billed. | A payment-policy engine: per-token spending allowances, session caps, allowlists, an activity log, and revocation, enforced server-side before enclave signing. This enforcement is tied to using Coinbase's managed wallet infrastructure; no position or drawdown limits are documented. |
| Chain focus | Solana. | EVM-first (Base primary); its Trade API offers 0x-powered DEX aggregation on five EVM chains. Solana support covers transfers and message signing only — no swap, lending, or perps action providers. |
| Perps / derivatives | Multi-venue on-chain adapter (Jupiter Perps primary; additional venues gated behind admin-updatable safety flags), non-custodial throughout. | On-chain: not documented. Derivatives are offered through "Coinbase for Agents" on Coinbase's centralized exchange (Coinbase Advanced) — a custodial exchange account, not an on-chain, non-custodial path. |
| MCP support | One hosted MCP endpoint (mcp.crank.ing) with 196 tools; also exported as OpenAI, Gemini, and LangChain tool definitions from the same registry. |
An official MCP integration/extension is available, covering a subset of actions. |
| Paper / simulate-first trading | Yes — real mainnet quotes, simulated fills, identical tool surface, graduates to live without code changes. | Not documented. |
| Durable agent memory | Private per-wallet decision journal with automatic outcome attribution (realized P&L, fees, slippage) across sessions. | Not documented. |
| License | Proprietary hosted service; MCP protocol is open. | The AgentKit SDK is Apache-2.0, open source. The CDP Server Wallet backend it connects to is a hosted Coinbase service, not open source. |
| Cost | Reads free; a technology service fee applies to value-bearing actions (volume-tiered, per-action floor — see the fee schedule). | Free, open source SDK; CDP platform wallet services are priced separately by Coinbase. |
The short version¶
If a TEE-secured, platform-operated wallet fits your architecture — for example because you want Coinbase's infrastructure to own key lifecycle and you're building primarily on Base or another EVM chain, where its DEX routing is genuinely strong — AgentKit's Agentic Wallets are a well-documented option with real hardware-backed key isolation. If you want TEE-grade isolation without platform custody — the key never leaves the wallet owner's own hands, on Solana, with trading guardrails (position and drawdown limits, kill switch with unwind) enforced on that same self-custodied wallet and a paper mode to prove the flow first — that is what Crank is built around. See the mechanics: How AI agents trade non-custodially.
Sources¶
- Wallet options, chain support (Solana = transfers and message signing only), MCP integration, license:
github.com/coinbase/agentkit— README and action provider listings, checked 2026-08-23. - Agentic Wallets GA (February 2026) and TEE architecture (AWS Nitro Enclaves, encrypted key storage, Wallet Secret access): Coinbase CDP announcements and
docs.cdp.coinbase.comsecurity documentation, checked 2026-08-23. - Policy engine (spending allowances, session caps, allowlists, activity log, revocation): Coinbase CDP Agentic Wallets / AgentKit guardrails documentation, checked 2026-08-23.
- Derivatives via Coinbase Advanced (centralized exchange account): "Coinbase for Agents" announcement (June 2026), checked 2026-08-23.
- Crank custody model, gate stack, venue adapter, fee schedule: this docs site — non-custodial trading guide, authentication & x402, fee schedule.
Comparison reflects Coinbase AgentKit's publicly documented capabilities as of the date above and may change; verify against its current documentation before depending on it. Coinbase AgentKit is a project of Coinbase; its name is used here for identification only, with no affiliation implied. Crank is a non-custodial technology provider, not a broker-dealer or investment adviser; nothing on this page is financial advice.