How Coinbase for Agents Connects AI Agents to Advanced Trade

Coinbase for Agents links AI agents to Advanced Trade via a remote MCP URL or a local CLI, requires an isolated funded portfolio and order previews, and uses retail USDC on Base for capped x402 payments.

Coinbase for Agents is an account connector that lets AI agents interact with Coinbase Advanced Trade for spot crypto, eligible equities and US derivatives in the default portfolio. Operators can connect an agent harness either to a remote MCP endpoint at https://agents.coinbase.com/mcp using OAuth or run a local @coinbase/coinbase-cli with a CDP API key for direct execution.

The remote path supports documented MCP clients; the documentation lists integrations such as ChatGPT in developer mode, Claude and other MCP-compatible clients. Operators using other models or seeking more predictable execution are advised to use the local CLI and a CDP API key configured for the agent portfolio with Trade and Transfer scopes.

The local CLI requires Node.js 22 or later and installation of @coinbase/coinbase-cli. Operators must create a CDP API key in the Coinbase portal, scope it to the agent portfolio, and enable Trade and Transfer. The Transfer scope only moves funds between Coinbase portfolios and does not permit withdrawals to external addresses. The key should be stored in the operating system keyring the CLI uses and rotated if exposed.

Operators must create a dedicated Advanced portfolio for agent use, fund it only with money they are prepared to lose, and limit OAuth approval or API key access to that portfolio. After connecting, list portfolios and confirm the portfolio UUID matches the funded account to ensure the agent is scoped correctly.

Every live order must be previewed before submission. Use coinbase orders preview or the MCP orders_preview tool to view estimated fills, fees and slippage, then call coinbase orders create only after a correct preview. Prompts must include an explicit product_id, portfolio, side, type and amount; the documentation warns that vague prompts can return the wrong product_id, for example ETH-USD instead of ETH-USDC.

Curated x402 research in the Coinbase catalog can be paid from a retail Coinbase USDC balance on the Base network without a separate provider key. Catalog discovery is free via coinbase x402 resources and MCP coinbase_x402_resources. Fetches use coinbase x402 fetch and accept a max_amount in atomic USDC units (1,000,000 = 1 USDC). Each settled payment is capped at 5 USDC and cannot exceed that ceiling; settled payments are irreversible on Base. Coinbase recommends generating and reusing an idempotency_key UUID when a payment outcome is uncertain.

Documentation separates research payments from trade authorization and notes that hosted high-reasoning clients sometimes draft orders without executing them. The local CLI is documented as the most consistent path for placing orders when hosted models decline or fail to act. Available tooling for equities is more limited than for spot crypto.

Before allowing unsupervised agent activity, perform a smoke test: verify the connector returns the expected portfolio UUID, confirm balances contain only intended funds, run an orders preview for a tiny notional amount and check fees, and perform a sub-1 USDC x402 fetch if research is in scope. Revoke remote MCP access via the Coinbase account Connections page or delete the CDP API key to remove the connector.

Coinbase for Agents provides account-level access inside a Coinbase Advanced Trade account. It differs from AgentKit, which is a developer wallet SDK for paying arbitrary x402 APIs, from a flow that provisions a dedicated agentic USDC wallet, and from merchant acceptance via Coinbase Business Checkouts. Operators should select the product that matches whether the agent will act inside a brokerage account or hold an independent wallet with programmatic spend controls.

Articles by this author