Skip to main content
Coinbase for Agents connects your AI apps to your Coinbase account for crypto, equities, and derivatives trading, portfolio management, and x402 payments. Your agent can pay for trading data and research from your existing Coinbase USDC balance, then use the results to inform trades you authorize.

Get started

Paste this prompt into your agent:
For this command, the Coinbase entry skill directs your agent to the Coinbase MCP setup guide. On a supported client, your agent reuses an existing connection or helps you sign in to Coinbase, then lists your portfolios to verify access. Use it in future chats: If your harness supports installed skills, ask your agent to adopt the guide using its documented skill mechanism. Reading a URL does not install a skill or guarantee discovery in a new chat. Preserve any existing connector and credential helpers; the guide explains how to add the instructions without replacing them.
Portfolio isolation: Create a separate Advanced portfolio, fund it with only what you’re willing to risk, and scope your agent’s access to that portfolio. This limits the blast radius if the agent makes an unexpected trade.
Disconnect: To revoke Coinbase access, go to Coinbase Account > Security > Connections and revoke the connection. If your agent cannot disconnect through the harness, do this yourself. Deleting a local skill or clearing a chat is not the same as revoking access.

What’s supported today

Coinbase for Agents currently supports:
  • Spot crypto trading: buy and sell 900+ trading pairs on Coinbase
  • US Derivatives (Futures): trade CFM dated futures contracts on Coinbase
  • Equities: trade eligible US stocks on Coinbase
  • Isolated agent portfolios: spot crypto only, scoped to a specific portfolio selected when logging in or creating an API key. US Derivatives (Futures) are available only in your default portfolio.
  • Portfolio management: Check balances and positions across your account
  • x402 payments (remote MCP and local CLI): pay for premium data services per-request from your USDC balance
  • Agent feedback: agents can send the Coinbase team short notes about the integration
Orders execute through Coinbase Advanced Trade, so Advanced Trade fees and eligibility requirements apply.
Coming soon: prediction markets and additional asset classes.

x402 payments

Your agent can pay per request for trading data and research, including onchain analytics, market intelligence, and stock data, directly from your retail Coinbase USDC balance. You don’t need a separate wallet, provider API key, or data subscription for these resources. The remote MCP uses Coinbase OAuth; the local CLI uses your configured CDP API key. Payments use USDC on Base through the x402 protocol.

Discover, pay, and use the data

  1. Discover: Call coinbase_x402_resources or run coinbase x402 resources q==<keyword>. Discovery is free and returns resource URLs, input schemas, and advisory pricing.
  2. Set a budget: Tell your agent how much it may spend on research. Research authorization does not authorize a trade.
  3. Fetch: Call coinbase_x402_fetch or run coinbase x402 fetch with a catalog resource URL and the required inputs. The tool handles the payment challenge and returns the resource response.
  4. Review: Ask the agent to cite the data, report what it spent, and propose a trade only if that is part of your instructions.
Tool availability depends on your account and client. The dedicated ChatGPT trading integration does not expose x402 tools. These instructions use the core remote MCP or the local CLI.

Limits and payment safety

  • Payments are capped at 5 USDC per payment. Additional account and spending controls may apply.
  • max_amount is an optional per-request ceiling for fetch, in atomic USDC units: 1000000 is 1 USDC. It can lower, not raise, the catalog payment ceiling. It does not set a session or daily budget.
  • Fetch accepts curated catalog resources and x402 v2 challenges. It is not an unrestricted web-fetch or Bazaar-discovery tool.
  • Generate an idempotency_key UUID before a payment and retain it. If a request times out or the payment outcome is unknown, reuse that key for the same logical payment; a new key can create another hold. Follow terminal-error instructions rather than retrying blindly.
  • A successful payment authorization does not guarantee that the provider returned usable data. Report payment and data-delivery outcomes separately.

Data providers

The curated catalog includes Arkham, Dripstack (listed as Drip), Exa, Glassnode, Massive, Nansen, and You.com. Run coinbase x402 resources or call coinbase_x402_resources for current resources, schemas, and advisory prices. The provider’s payment challenge determines the exact price, subject to your request ceiling and server limits. Catalog inclusion does not guarantee provider availability.
Try: “Use Coinbase x402 to research ETH smart-money flows. Spend no more than 1 USDC total, cite the data and what you paid, and do not place any trades.”
Settled x402 payments are irreversible and recorded on Base. Set a research budget before authorizing paid requests; an instruction to the agent is not a server-enforced session spending limit.

Guiding agents to place orders

Based on order-creation testing across Claude and ChatGPT clients and models connected to the Coinbase for Agents remote MCP server:
  • Web clients for Claude and ChatGPT reliably create orders from clear, well-specified instructions, across models. The exception is GPT-5.5 Pro, which doesn’t appear to automatically discover the connected MCP.
  • Claude previews and requests confirmation in the chat to create the order, whereas ChatGPT creates the order in one turn.
  • Claude Desktop refuses most orders that the web client creates; Sonnet 4.6 is the exception, creating orders when the request includes an explicit authorization (e.g. I authorize you to buy…).
  • Lower-tier models may create orders with the wrong product, for example, ETH-USD instead of ETH-USDC. Prompt for approval to confirm before creating the order.
For reliable order creation, specify the order type, the amount and asset or currency, and the portfolio in one instruction, for example, Buy 1 USDC of ETH in my agent portfolio. Vague or partial requests require the model to infer and resolve additional details.

Best practices

  • Scope the agent’s access to the portfolio(s) you want it to use. A focused set gives the agent a clear, unambiguous target.
  • Higher-reasoning models translate more complex intent and recover from underspecified orders; use one for multi-step or vague requests, e.g. check my balance, then put 5% of my USDC into BTC.

Send feedback

You or your agent can send feedback about the Coinbase MCP directly through the coinbase_feedback_submit tool. Submit a prompt in this form: Tell Coinbase that [your feedback]. The team reads submitted feedback every day.
  • Feedback is limited to 2,000 characters or less.
  • Each user can send up to 6 submissions per day.

Tools

The tables use short MCP tool names. The core server prefixes these with coinbase_ (for example, coinbase_portfolios_list); use the exact names returned by your connection’s tools/list.

Market data

Equities: Use products_get or products_list for a reference price, not a guaranteed executable quote. Do not assume equity ticker, order-book, bid/ask, candle, or preview support from a successful product lookup. See the agent guide’s product-type limitations before building an equity workflow.

Orders

Market order: executes immediately at the best available price.
Limit order: executes at the specified price or better.
Market buys use quote_size (the amount to spend in USD). Market sells use base_size (the amount of the asset to sell). When switching between buy and sell, explicitly clear the other field (e.g., add quote_size= to clear a stale value).
Futures: CFM dated futures market orders require base_size (number of contracts)—quote_size is rejected. Contract codes roll on a schedule (e.g. BIT-28AUG26-CDE); discover the live one with coinbase products list product_type=FUTURE. Preview the order first to check predicted_liquidation_price.
Equities: use TICKER-QUOTE as the product ID (e.g. AAPL-USD or AAPL-USDC). Discover eligible tickers with the product tools. Orders trade regular market hours by default; check the current tool schema for supported sessions, order types, and sizing restrictions.

Portfolios and balances

Conversions

x402 payments

Feedback

Info and session


Global flags

These flags work on any CLI command:

Field syntax

CLI commands use the following field syntax:

Troubleshooting


Disclaimer

AI agents can make errors, misinterpret instructions, or produce inaccurate output. Coinbase does not guarantee the accuracy of any action taken by an AI agent using this product. You are solely responsible for reviewing and authorizing any trades, transfers, or account changes made through agentic workflows.