Skip to Content
WaaP for AgentsFrameworksCoinbase AgentKit

Coinbase AgentKit

Coming Soon — The WaaP wallet provider for AgentKit is under active development and not yet available for use. This page describes how the integration will work when released.

Coinbase AgentKit  is a TypeScript framework for building on-chain AI agents. WaaP will provide a drop-in wallet provider that replaces AgentKit’s default CDP (Coinbase Developer Platform) wallet with two-party signing.


How the integration will work

The WaaP wallet provider will implement AgentKit’s EvmWalletProvider interface. All existing AgentKit actions (transfer, swap, deploy, etc.) will work without changes — you swap the provider, and everything downstream stays the same.

Provider configuration

When available, the provider will accept the following configuration:

interface WaapWalletProviderConfig { /** Path to the waap-cli binary. Defaults to "waap-cli". */ cliPath?: string; /** EVM chain ID (e.g. "8453" for Base). */ chainId: string; /** RPC URL for the target network. */ rpcUrl?: string; /** Email for waap-cli login. If provided with password, auto-login on configure. */ email?: string; /** Password for waap-cli login. */ password?: string; }

Swap from CDP to WaaP

When released, switching from CDP to WaaP will be a one-line change at the provider level. You replace CdpWalletProvider with WaapWalletProvider, and the rest of your agent code stays identical.


How it will work under the hood

The WaapWalletProvider will shell out to waap-cli for every signing operation:

  • getAddress() calls waap-cli whoami
  • signMessage() calls waap-cli sign-message
  • signTypedData() calls waap-cli sign-typed-data
  • signTransaction() calls waap-cli sign-tx
  • sendTransaction() calls waap-cli send-tx

Read operations (balance, contract reads) go directly through a Viem PublicClient — no CLI call needed.

The CLI handles two-party signing, policy checks, and Telegram approval flows transparently. Your AgentKit code never touches a key.


Last updated on