Anthropic bought Stainless, the startup that builds every official SDK for OpenAI and Google.

Anthropic announced on May 18 that it had acquired Stainless, the SDK and MCP server toolchain that quietly underpins every official Claude client library. The same toolchain also generates OpenAI’s, Google’s, and Cloudflare’s official SDKs. Anthropic did not disclose terms; The Information reported the price north of $300 million.

The structural read is sharper than the price tag. A model lab just bought the company that turns its rivals’ API specs into production client libraries. Stainless customers told TechCrunch the hosted product is being wound down. They will keep the SDKs already generated. They will not get new ones from the same pipeline.

Who Stainless is

Stainless was founded in 2022 by Alex Rattray, an engineer who previously worked on Stripe’s API tooling. The company turns an OpenAPI spec into idiomatic SDKs across Python, TypeScript, Go, Java, Kotlin, and a handful of other targets, then keeps the SDKs in sync as the spec changes. The pitch was simple: every API company pays a small team to maintain seven language clients by hand. Stainless replaced that team with a code generator that the API company would otherwise have to build in-house.

The customer list is the part that matters this week. Anthropic’s own press release confirms Stainless has “powered the generation of every official Anthropic SDK since the earliest days of the API.” TechCrunch confirms the same is true at OpenAI, Google, and Cloudflare. Sequoia Capital and Andreessen Horowitz led prior rounds; both VC firms are now cashed out, as is Rattray.

Two short statements went out with the announcement. Anthropic’s Katelyn Lesse, Head of Platform Engineering, said “agents are only as useful as what they can connect to.” Rattray said “SDKs deserve as much care as the APIs they wrap.” The team and the codebase move to Anthropic.

The wind-down

What Stainless customers actually need to know is on the Benzinga readout and confirmed by Anthropic to TechCrunch. The hosted Stainless platform, the one rivals run their spec changes through, is being wound down. Customers retain full ownership of every SDK already generated and can modify or extend those SDKs however they want. They cannot regenerate from the same pipeline against future spec changes.

That puts OpenAI and Google in a tight spot. The official openai-python and openai-node libraries on PyPI and npm are not going to disappear next week. But the next time those API specs change in a way the client needs to support, OpenAI’s release engineers have to either fork the generator, rebuild it, or ship the client by hand. The same is true for Google and Cloudflare. There is no public ETA on the wind-down; the announcement says “we’ll work with customers to ensure a smooth transition.”

What this is actually about

Anthropic’s framing of the deal is agent connectivity. The press release puts MCP at the center: Stainless ships an MCP server generator that can turn an API into a tool-callable target for a Claude agent in a few minutes. Anthropic invented the MCP spec last year. Bringing the team that has been building the most mature server generator in-house is the AI-lab move; preventing rivals from running the same pipeline is the strategic-acquisition move. Both readings are correct at the same time.

What it isn’t is a defensive acqui-hire. Anthropic’s own SDKs already ran on Stainless. The team was already integrated with Anthropic’s platform engineering org in practice. The acquisition formalizes that and removes the wedge a competitor could have used to acquire Stainless first.

What this means for you

If you ship API products and use Stainless, lock in a regeneration of the SDKs you care about now, against the current spec, and plan the migration to a different generator or hand-maintained client over the next two quarters. The realistic alternatives are Smithy (AWS-built, mature, more verbose), Speakeasy (the closest competitor to Stainless on developer experience), or rolling your own from openapi-generator. None ship MCP-ready output the way Stainless did; you may end up running two tools.

If you build agentic applications on Claude, the integration story gets a tighter end-to-end pipeline. Expect the next Claude SDK refresh to land first-class MCP wiring out of the box, and expect agent tool-calling to get faster to set up against arbitrary APIs. The downside, if you’re not on Claude, is real: the most useful pipeline for shipping an MCP-callable interface for your service is now owned by the AI lab whose model you may not be using. That’s the cost Anthropic just paid $300 million plus to impose on its competition.