Before an agent spends,
show what it can read.

OUR ASSESSMENT

A useful idea, with real boundaries.

Our interest is practical: can an agent gather useful information, explain its evidence and stop at the right boundary? Coinbase for Agents is worth studying as an interface between a conversation and an account. This first pass supports a review of its documented design, not a verdict on trading reliability or investment performance.

For an independent learning project, the useful lesson is to make each step visible: a public read, an account connection, a spending permission and a completed payment are different results. Our experiment reached the public read and the authentication boundary.

FIRST-PERSON OBSERVATIONS

What we actually tried

1. Read a public price

   At 5:00:26 AM PST, our local test sent an unauthenticated GET to Coinbase's BTC–USD spot endpoint. It returned HTTP 200 and a JSON price response. This was a dated observation, not an executable quote. Read the test receipt.

   The official price documentation says, This endpoint doesn’t require authentication. That is why this successful request does not demonstrate private account access. Source 1.

2. Check the account boundary

   At 5:02:16 AM PST, an unauthenticated MCP initialization request to Coinbase's account server returned HTTP 401 with the response unauthorized. We stopped. We did not attempt OAuth, connect an account, configure credentials, place an order or buy data. Read the test receipt.

   The account-server documentation specifies OAuth for remote access. A rejected request without authentication does not establish that an authorized client would fail. Source 2.

DOCUMENTED FACTS / CHECKED NOVEMBER 3

What the product promises

Coinbase describes an account connection for market information and trading. Crypto, stocks and futures depend on region and account eligibility. It says there is no added product fee, while ordinary trading fees still apply. Its US data-payment FAQ states a $5 per-payment and $50 daily cap. These are vendor descriptions, not features we exercised. Source 3.

One distinction matters: isolated agent portfolios cover spot crypto. US futures use the default portfolio. Client approval and available tools also matter; general MCP compatibility alone does not assure access. The retail x402 fetch tool accepts curated catalog resources. A payment ceiling does not show that a payment settled or that useful data arrived. Source 2.

A SEPARATE BUILD

Buying data does not make a site a seller.

Coinbase's seller quickstart describes a different implementation: a paid HTTP route with a payment challenge, a receiving address, verification and settlement. Connecting a buyer's account does not implement those server responsibilities. We did not build a paid endpoint or test settlement for this review. Source 4.

Our next proposed step: produce a repeatable public-data briefing with dated receipts. A private-account test would be a separate, explicitly authorized experiment with its own access scope. Selling a service would require a separate design and cost decision. Neither is part of this publication.