Summary: Anthropic confirmed on May 18, 2026 that it acquired Stainless, a developer-tools company whose tooling generated SDKs, CLIs, and MCP servers from API specs. Stainless’s hosted products immediately stopped new signups, projects, and generations, so existing API teams must maintain their generated SDKs or find alternatives. The article says the reported valuation exceeded $300 million, while the actual price stayed undisclosed.
Anthropic confirmed on May 18, 2026 that it has bought Stainless, a startup in the developer tools business. The job itself sounds mundane: feed in an API spec, get back SDKs, CLIs, and MCP servers in every major language, all kept current as the spec moves. The customer roster is what turns heads, though — OpenAI, Google, Cloudflare, Replicate, and Runway — placing Stainless among the infrastructure half the AI industry leaned on. A week ahead of the announcement, The Information reported that talks valued the company north of $300 million; what was actually paid has never been made public.
What matters here is less the price tag than what the deal changes: as of announcement day, Stainless’s hosted products accept no new customers, and the whole toolchain now serves Anthropic alone. Picture a highway every lab drove on; one of the drivers bought it and turned it into a private lane.
Stainless’s Core Business
Stainless, started in 2022 and headquartered in New York, took on a chore familiar to any API team: reading a spec and emitting production-grade SDKs in Python, TypeScript, Kotlin, Go, Java, and other languages, with synchronization handled automatically whenever the API moves, so nobody maintains the wrappers by hand. Later, the same machinery learned to generate CLIs and MCP servers, and MCP servers land exactly where agents need to hook into outside software.
By reach, the company dwarfs its profile: on Stainless’s own estimate, close to one in four professional developers worldwide has touched an SDK or docs site produced with its tooling. Anthropic, meanwhile, has never shipped an official SDK that Stainless didn’t generate, going back to the API’s first release. The partnership runs deep — Stainless says it was part of nearly every Claude API launch — which makes the buyout feel less like a shock and more like paperwork.
Terms and Price Tag
The company’s founder, Alex Rattray, previously engineered at Stripe, and its backers included Sequoia Capital and Andreessen Horowitz. With the actual price kept quiet, The Information’s “above $300 million” remains the only number the public has. Rattray did not dress up his reasoning: “I started Stainless because SDKs deserve as much care as the APIs they wrap,” he wrote, describing the move to Anthropic as an easy call and adding that nowhere else would let the team build the future of internet software.
What Made the Purchase Necessary
The strategic case comes down to a sentence from Katelyn Lesse, who heads Platform Engineering at Anthropic: “Agents are only as useful as what they can connect to.” MCP is Anthropic’s own protocol, and the connectors plus tooling that wire agents to APIs are precisely Stainless’s craft. Owning that layer puts the Claude ecosystem’s developer experience — from the model itself down to every integration — under Anthropic’s direct control.
The defensive angle is impossible to ignore either: Stainless counted OpenAI, Google, and Cloudflare among its customers. Now that the deal has closed, the tooling is off the table for their future work — a supplier the rivals shared belongs solely to one lab.
Aftermath of the Shutdown
Existing customers absorb the damage. Every hosted product, the SDK generator among them, immediately stopped taking new signups, new projects, and new generations; those already on the platform are steered toward a transition guide at app.stainless.com/transition. Ownership of SDKs already generated stays with the customers, who may modify and extend them freely. Rattray closed with a case for why the work still matters — “Great APIs are more essential now than ever,” he wrote, now that agents read and call them at machine scale. The net effect: what was generated keeps working, nothing new gets generated — each affected API team must either stand up its own maintenance pipeline or shop for a different vendor.
Seen from a distance, the deal is the 2026 consolidation wave in small form. Compute and talent are no longer the only items on frontier labs’ shopping lists; the developer toolchain, upstream and downstream, is being bought piece by piece. The “ecosystem land grab” outlined in our opening-of-year outlook is coming due. The takeaway for developers is concrete: if you lean on one third-party toolchain, add a new entry to the risk list — your vendor can be bought by its own customer.