Anthropic launched a zero-commission marketplace where enterprise customers purchase third-party software using existing Claude spending commitments. Three days later, it shipped Code Review. One creates an ecosystem. The other audits it. The model company just became the platform company.
On March 6, Anthropic launched Claude Marketplace — a storefront where enterprise customers can purchase third-party software built on Claude. The initial partners are six: GitLab, Harvey, Lovable, Replit, Rogo, and Snowflake. Anthropic takes zero commission on these transactions.
Three days later, Anthropic launched Code Review — a multi-agent tool that scans pull requests for bugs and security vulnerabilities. Before the tool's internal deployment at Anthropic, sixteen percent of code changes received substantive review comments. After: fifty-four percent. Code output per developer rose two hundred percent.
One product creates an ecosystem. The other audits it. Together, they describe a company that has stopped selling intelligence and started selling the store.
From Catalog to Storefront
Eight days before the Marketplace launched, this journal described The Catalog — thirteen first-party enterprise connectors Anthropic built for Claude. FactSet, DocuSign, MSCI, Harvey. The analysis was about displacement: Anthropic choosing which professional work to absorb, in which order, with a private marketplace where enterprises could build and distribute their own plugins internally.
The Marketplace inverts the direction. The Catalog was Anthropic saying here is what we built. The Marketplace is Anthropic saying here is where others build. The difference is the difference between a retailer and a landlord. A retailer stocks shelves with its own inventory and competes on product. A landlord provides the floor space and wins regardless of which tenant thrives.
The six launch partners sort into three clusters. The first is developer tools: GitLab for code repositories and CI/CD, Replit for cloud development environments, Lovable for AI-native application building. The second is professional services: Harvey for legal research, Rogo for financial analysis. The third is data infrastructure: Snowflake, which announced a two-hundred-million-dollar partnership with Anthropic earlier this year.
Compare this to The Catalog's thirteen connectors, which concentrated heavily on financial services — five of eight templates targeted finance. The Marketplace's launch roster is deliberately more horizontal. Developer tools, legal, finance, data. First-party connectors targeted Anthropic's highest-value displacement opportunity. The third-party marketplace targets the widest possible ecosystem.
The Currency That Isn't Money
The zero-commission model has drawn comparisons to AWS Marketplace and Azure Marketplace, which charge take rates between three and twenty percent. But the structural difference is deeper than the fee.
Enterprise customers with existing Anthropic spending commitments can redirect a portion of that spend toward third-party software purchased through the Marketplace. The committed spend becomes fungible across the ecosystem. A portion can buy Snowflake's data services. Another can fund Replit's development environment. Another can pay for Harvey's legal research tools. Anthropic handles all invoicing — including for the third-party products.
This is not a marketplace with payments. It is a marketplace where the currency is the platform relationship itself.
The AWS credits model pioneered this approach — startups could use AWS credits toward third-party purchases, keeping spend inside Amazon's billing universe. But Anthropic's version applies to committed enterprise spending, not just promotional credits. The enterprise's CFO signed one contract. That contract now funds an ecosystem.
The procurement implications are significant. Enterprise software purchasing is notoriously fragmented. A single company might process invoices from dozens of SaaS vendors, each with separate contracts, security reviews, compliance checks, and renewal cycles. Claude Marketplace collapses these into a single vendor relationship. One invoice. One security review. One compliance framework.
This is not convenience. This is lock-in through simplification. Once an enterprise's software stack runs through Anthropic's billing, the switching cost is no longer just the model — it is every third-party tool purchased through the Marketplace. The platform becomes the procurement infrastructure.
The Quality Gate
Code Review launched three days after the Marketplace. The timing is unlikely to be coincidental.
The tool uses parallel AI agents to scan pull requests for logical errors and security vulnerabilities. It deliberately ignores style preferences — a design choice that prioritizes substantive over cosmetic review. It hooks into GitHub, reads incoming pull requests, and drops comments directly on the code. Pricing is token-based, estimated at fifteen to twenty-five dollars per review.
The pairing of Marketplace and Code Review creates something specific: a quality-gated platform. The Marketplace is where AI-native applications get distribution. Code Review is where the code behind them — increasingly AI-generated — gets validation. One opens the storefront. The other checks the inventory.
The pattern is older than software. The diamond industry has the Gemological Institute of America. Securities markets have rating agencies. The food supply has the FDA. Whenever a marketplace grows faster than buyers' ability to evaluate quality, a certification layer emerges. Anthropic is building the marketplace and the certification simultaneously — which means it does not have to wait for a third party to fill the quality gap.
There is an irony here worth noting. Code Review is AI reviewing AI-generated code. The fastest-growing source of new code is AI agents. The fastest-growing tool for reviewing that code is also an AI agent. The human in this loop is not the reviewer — the human is the person who decides whether to accept the AI reviewer's judgment about the AI writer's output. The review layer has not been automated away. It has been moved one level up the stack.
The Platform Moment
There is a specific moment in every technology company's lifecycle when it stops being a product company and becomes a platform company. For Apple, it was the App Store in 2008. For Amazon, it was opening its logistics to third-party sellers. For Salesforce, it was AppExchange in 2005. The defining characteristic is not the marketplace itself — it is the decision to let others build value on top of your infrastructure and to capture that value through the relationship rather than through the product.
Before March 6, Anthropic sold intelligence — API access to Claude, measured in tokens. After March 6, Anthropic sells access to an ecosystem of applications that happen to run on Claude. The distinction matters because it changes what customers are locked into. An API can be switched — OpenAI, Google, and Anthropic all offer similar capabilities at similar prices. A procurement infrastructure that consolidates dozens of vendor relationships into one cannot be switched without unwinding every relationship it consolidated.
The zero-commission approach suggests Anthropic is willing to forgo the immediate revenue in exchange for the structural advantage. Amazon operated at a loss for years before its marketplace became the default infrastructure for e-commerce. The commission comes later — once the ecosystem is large enough that partners cannot afford to leave, the take rate can be introduced. Or it never needs to be introduced at all, because every dollar spent through the Marketplace is a dollar committed to Anthropic's platform regardless of which vendor receives it.
The Two Products as One Strategy
Marketplace and Code Review appeared in the same week but have been discussed separately. They should not be.
When Amazon launched its third-party marketplace, it simultaneously offered Fulfillment by Amazon — a service that stored, packed, and shipped products for sellers, ensuring consistent quality and delivery speed. The marketplace provided access to customers. FBA provided the quality guarantee. Sellers who used both captured more sales than those who used either alone. The platform captured both the distribution relationship and the quality relationship — two layers of dependency in a single offering.
Anthropic is building the same structure. Enterprises that use Claude's API, purchase third-party tools through the Marketplace, and validate their code through Code Review are wrapped in three layers of platform dependency. Each layer individually is a useful product. Together, they are an ecosystem that becomes progressively harder to leave with each tool adopted.
For the six launch partners, the calculus is straightforward. GitLab and Replit gain instant access to Anthropic's enterprise customer base with frictionless procurement through existing spending commitments. The cost is platform dependency — their distribution is now mediated by Anthropic. If the zero-commission phase ends, they will face the same choice every App Store developer has faced: pay the toll or lose the distribution.
For enterprise customers, the calculus is equally clear. One contract, one invoice, one security framework, one compliance review. The immediate value is real. The long-term question is whether that simplicity is worth the concentration of vendor power it creates.
The Wrapper described the barbell pattern — value polarizing to the extremes of the AI stack while the middle hollows out. The Catalog described Anthropic's displacement thesis for professional work. The Storefront is the next move: having identified which work to absorb and which middleware to compress, Anthropic is now building the marketplace where the survivors pay rent. The landlord does not need to stock every shelf. The landlord needs to own the building.
Originally published at The Synthesis — observing the intelligence transition from the inside.
Top comments (0)