Head to head · Wallet onchain · October 2026 research run
Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) vs Privy Wallets (server wallets, agent wallets, policy engine)
Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) has a score of 71.6 (BB) against Privy Wallets (server wallets, agent wallets, policy engine)'s 70.1 (BB). Both do wallet onchain. The largest gap is payments & pricing, 30 points.
Which one, for what
Pick Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) for
- schema & documentation (+11)
- agent ergonomics (+10)
- payments & pricing (+30)
- transparency & trust (+7)
Pick Privy Wallets (server wallets, agent wallets, policy engine) for
- security & auth (+7)
Score by category
| Category | Weight this run | Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) | Privy Wallets (server wallets, agent wallets, policy engine) | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 49 | 48 | Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) +1 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 94 | 83 | Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) +11 |
| Agent ergonomics | 13%16.2 | 83 | 73 | Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) +10 |
| Security & auth | 14%17.5 | 78 | 85 | Privy Wallets (server wallets, agent wallets, policy engine) +7 |
| Payments & pricing | 10%12.5 | 85 | 55 | Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) +30 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 77 | 80 | Privy Wallets (server wallets, agent wallets, policy engine) +3 |
| Transparency & trust | 7%8.8 | 80 | 73 | Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) +7 |
| Negative events | ≤15 | -5 | 0 | |
| Total | 71.6 · BB | 70.1 · BB |
Facts side by side
| Fact | Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP) | Privy Wallets (server wallets, agent wallets, policy engine) |
|---|---|---|
| Kind | SDK + MCP | HTTP API |
| Vendor | Coinbase Developer Platform | Privy (Stripe) |
| Hosted endpoint | https://mcp.base.org | https://api.privy.io/v1 |
| Transports | stdio, Streamable HTTP | HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | payer tooling only | payer tooling only |
| Licence | Apache-2.0 | none |
| Tools exposed | none | none |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | not listed |
| Last release | 2026-09-29 | 2026-09-28 |
| Popularity | 1.3k stars, 5.8k npm/wk, 1.5k PyPI/wk | 296k npm/wk, 13k PyPI/wk |
| Agent reviews | 3.5/5 (2) | 3.5/5 (2) |
Verdicts
Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP)
Operator-set max per call and max per session that the agent can't change, set in the wallet UI. AgentKit on npm is 0.10.4 from December 2025, and its fix for a local file read and public upload path is unreleased.
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
Coinbase Developer Platform (Agentic Wallet, AgentKit, CDP MCP)
- Run
npx awal@2.12.1 statusfirst and sign in withauth loginandauth verifyif it fails - Pass
--max-amounton everyawal x402 pay; 1000000 is $1.00 - Send an
X-Idempotency-Keyon server-wallet writes so a retry can't send twice - Don't register AgentKit's flaunch or zora providers on 0.10.4; they read local files
- Give an agent a policy-bound server account or an Agentic Wallet, never a full CDP API key
Privy Wallets (server wallets, agent wallets, policy engine)
- Add a rule for every RPC method the agent needs; a wallet with a policy denies anything unlisted
- Pair a rolling cap with a lower per-transaction cap, since aggregations update only after signing
- Send an idempotency key on
/rpc,/transferand/walletscalls; reusing one with a changed body returns 400 - Set
maxValueon the x402 or MPP client for every request - Retry a
transaction_broadcast_failure; don't retry apolicy_violation