The Plumbing: How an MCP Server, Sub-Accounts, and a Dormant HTTP Code Add Up to an Autonomous Trader
Strip away the framing and Coinbase for Agents is three pieces of infrastructure clicked together. The first is the connection layer: a Model Context Protocol (MCP) server that lets web-based assistants like ChatGPT and Claude reach into a Coinbase account, plus a command-line tool for developers working in a terminal [2]. MCP is the emerging open standard for giving an AI model structured, permissioned access to an external system — here, that system is a live brokerage. The second piece is containment: rather than handing an agent the keys to everything, a user can point it at a dedicated sub-account, an isolated portfolio with no visibility into their main holdings [3]. At launch the agent can trade spot crypto and derivatives, with equities and prediction markets on the roadmap [1]. The third piece is the payment rail, and it is the most interesting. The x402 protocol — built by Coinbase with AWS, Anthropic, Circle, and Near — is an open machine-to-machine payments standard [2]; in their own interviews and explainers, Coinbase's developer-platform team frames it as repurposing HTTP 402, the 'Payment Required' status code long dormant in the web's plumbing, into a settlement layer that software can call. Developers in community threads add that it settles on Base using pre-signed authorizations, clearing in roughly two seconds at a fraction of a cent — cheap enough that an agent can pay per-call for a data feed or a research API instead of holding a subscription. Payment support was billed as arriving the week after launch [3].



