Claude Marketplace: Buying Agent Tools From Claude Spend

Anthropic launched Claude Marketplace on September 23, 2026. It is a single catalogue where teams find connectors, agent products and service partners that work with Claude, and where builders and partners reach Claude customers. The line that matters to a buyer is one sentence in the announcement: teams can use a portion of their committed Anthropic spend on marketplace purchases.

That sentence moves an agent purchase from a new budget request to a drawdown on money already approved. It is the same mechanism the cloud marketplaces have used for years, and it is why a marketplace listing is a procurement event, not a directory entry. The rest of this post is about what changes for the buyer and what to check before drawing down.

Everything here comes from Anthropic's announcement. The percentage of committed spend that can be applied is not stated, and we do not guess at it.

The announcement describes the marketplace as live on the day. For builders the route in is to create a connector or plugin with MCP and Agent Skills and submit it, to apply to list a Claude-powered product, or to join the partner network for a services listing. Our earlier post on agent marketplaces as distribution covers how these catalogues have worked at other vendors; the new element here is the money.

A committed-spend contract is money a company has already agreed to pay a vendor over a period, usually in exchange for a discount. Once signed, it sits on the finance side as a line that will be spent. Letting a customer apply part of that line to third-party purchases changes three things at once.

First, the approval is already done. A team buying an agent product through the marketplace is not asking for new money; it is choosing how to use money the company has committed to Anthropic. The request that used to need a business case now needs a click and a check that the drawdown is within the allowed portion. Second, the contract path shortens. Purchases that would each have gone through vendor onboarding, security review and a separate invoice arrive through one relationship. Third, the incentive on the buying team flips. Unused commitment is a cost; a marketplace turns it into something the team can spend before it expires.

All three make it easier to buy. None makes the purchase safer, which is why the next section exists.

A marketplace listing built on MCP is an MCP server with a storefront. Every question we already ask of a connector applies. The routing below adds the ones that the money introduces.

Two of our reference pages carry the detail. The MCP security incident ledger records what has gone wrong with connectors in production, and the vendor claim due-diligence checklist is the list to run on any product before the drawdown.

The third category is the unusual one. Consultancies do not usually sit in a software catalogue next to the software. Putting them there does two things for a buyer. It makes an implementation partner a line item in the same purchase as the product, which suits companies that want one decision rather than two. And it invites comparison between a services engagement and a product on the same page, which favours firms that can describe an outcome rather than a headcount.

For the service firms themselves, it sets the terms of entry: the partner network, not a direct listing. Anthropic names three large consultancies at launch. Whether smaller firms appear, and on what terms, is not stated in the announcement, and this post makes no claim about who will or will not be listed. What is clear is that the catalogue rewards firms whose work can be bought in units, which is a shift many agencies, including ours, are already making in how we package AI transformation work.