Anthropic acquires Stainless and cuts off the SDK pipeline OpenAI and Google were sharing

verified

Tuesday, May 19, 2026

The News

Anthropic acquired Stainless, the New York–based dev-tools startup whose SDK generation software is used by OpenAI, Google, and Cloudflare. The company told TechCrunch it will wind down all hosted Stainless products, including its SDK generator. According to prior disclosures by The Information, the acquisition price was at least $300 million, effectively doubling Stainless's $150 million valuation from last December. "The frontier of AI is shifting from models that answer to agents that act," Anthropic's announcement reads. Stainless has powered the generation of every official Anthropic SDK since the earliest days of its API, and hundreds of companies rely on Stainless to generate SDKs, CLIs, and MCP servers (Anthropic).

The Read

Read this as Anthropic buying a chokepoint, not a team. OpenAI previously abandoned in-house SDK development and fully shifted to Stainless; all three leading model providers — OpenAI, Google, and Anthropic — currently rely on Stainless to generate their SDKs. Anthropic just removed two of those three from the supply. The deeper move is in MCP: Stainless was already generating MCP servers, the connectors agents use to actually reach external systems, and Anthropic invented MCP. That's not a developer-experience acquisition — that's the company that owns the protocol buying the company that owns the build tooling for the protocol. The model layer is commoditizing; the connectivity layer is being enclosed.

Counterview

Existing customers keep their SDKs, MCP is still under the Linux Foundation's Agentic AI Foundation, and competitors will fund Speakeasy/LibLab into adequacy within a year — a six-month moat, not a permanent one.

Do This Week

Pull the list of every AI vendor whose SDKs your team currently depends on and mark which ones were Stainless-generated. For each one, write down what changes if the underlying generator quietly degrades over the next two quarters. That document is your migration prioritization, and you want it before the first SDK update arrives late.

For Engineering lead