Anthropic Acquires Stainless: The SDK Engine Behind OpenAI, Google APIs

Anthropic announced this week that it has acquired Stainless, the New York-based developer-tools startup whose auto-generated SDKs are used by OpenAI, Google, Cloudflare, Merge, and a long list of other API-first companies. Reports placed the deal at more than $300 million. The move is a clear signal that Anthropic intends to win the developer experience layer around Claude — and is willing to buy one of the most strategically positioned dev tools companies in the industry to do it.

The acquisition closes a small irony: the company that builds the libraries most developers use to call OpenAI's API now belongs to OpenAI's largest direct competitor.

What Was Announced

Anthropic confirmed the deal on May 18. Stainless, founded in 2022 by former Stripe engineer Alex Rattray and backed by Sequoia Capital and Andreessen Horowitz, will join Anthropic to focus on Claude's developer experience and agent connectivity. The company's flagship product — automated SDK generation from OpenAPI specifications — has powered consistent, idiomatic libraries across Python, TypeScript, Java, Go, Ruby, and Kotlin for dozens of major API providers.

Anthropic put the strategic framing simply: "Stainless has powered the generation of every official Anthropic SDK since the earliest days of our API." That is, the acquisition formalizes a partnership that already existed. What changes is that Stainless will now build for Claude first.

Hosted Stainless products — including the public SDK generator service used by other companies — are being wound down. Existing customers retain full ownership of the SDKs they have already generated and can continue modifying and extending them. New customers cannot sign up.

Why This Matters

SDK quality is one of the least discussed but most important differentiators in API competition. When a developer evaluates Claude versus GPT versus Gemini, the first concrete experience is often importing the SDK, calling the API, and seeing how the types and errors behave. A polished SDK signals that the company takes integration seriously. A rough one creates friction that often costs the entire customer.

For most of Claude's history, that friction has been minimal precisely because Anthropic was a Stainless customer. The Python and TypeScript SDKs developers actually use to talk to Claude were generated by the same engine generating OpenAI's libraries. Bringing Stainless in-house removes a dependency, but more importantly, it lets Anthropic build SDK features specifically tuned to Claude's evolving agent and tool-use surface.

The competitive read is sharper. OpenAI now has to decide whether to keep using a tool owned by its main rival, build an equivalent in-house, or commission a new partner. Same for Google and Cloudflare. None of those decisions are urgent — current generated SDKs continue to work — but the relationship is fundamentally different now.

What Changes for Developers

In the short term, almost nothing. Anthropic SDKs keep getting better; Claude's API surface keeps expanding. The Stainless team, including founder Alex Rattray, joins Anthropic and continues working on SDK generation — just for one customer.

In the medium term, the practical implications are significant. Stainless's approach is opinionated about how SDKs should look across languages: consistent naming, idiomatic patterns, strong typing, useful errors, predictable streaming behavior. Those design choices now translate directly into Claude's SDKs, with no negotiation between vendor and customer.

Anthropic has been emphatic that the priority is agent connectivity. That maps to a specific roadmap: tighter MCP (Model Context Protocol) integrations inside the SDKs, better tool-calling ergonomics, first-class support for streamed agent state, and developer ergonomics around persistent multi-turn execution. The Managed Agents API and the Claude Agent SDK both benefit directly from Stainless-level polish.

Industry Impact

The acquisition is part of a broader pattern: AI infrastructure is consolidating into the hands of the leading labs. Anthropic has spent the past year acquiring or hiring its way into the parts of the developer stack that matter most for agent workflows — payments, retrieval, evaluations, now SDK generation. OpenAI has been making similar bets, including its recent buyout of an evaluation tooling vendor. Google's Gemini team has been integrating tooling acquisitions from Alphabet's broader portfolio.

What makes the Stainless deal stand out is that it touches every API competitor at once. Most acquisitions are about adding capability. This one is about removing a shared dependency from the rest of the field.

For startups in the broader API tooling ecosystem, the strategic question becomes whether to align with one frontier lab or position as cross-lab infrastructure. Stainless chose the first path. Expect the next wave of dev-tools rounds — observability, evals, agent frameworks — to face the same pressure.

What Industry Insiders Are Saying

Reaction in developer communities has been broadly positive, with the dominant framing that better SDKs benefit everyone using Claude. Some OpenAI and Google developers have raised concerns about long-term continuity of the SDKs they currently depend on, though Stainless has explicitly committed that already-generated libraries remain owned by the customer.

The acquisition has also been read as a signal about Anthropic's broader product strategy. The company is increasingly positioning itself as the developer-first frontier lab — Claude Code, Claude Agent SDK, Claude Cowork, and now Stainless — in contrast to OpenAI's more consumer-app-oriented posture and Google's productivity-first strategy.

What's Next

Watch for three things in the coming months. First, Claude SDK releases that take advantage of in-house ownership: deeper tool-use ergonomics, agent-state primitives, MCP first-class integration. Second, the wind-down timeline for hosted Stainless services — existing customers should plan for migration even if no immediate change is required. Third, whether other major API providers announce successor SDK strategies.

For developers currently building on Claude, the immediate action is none. Keep using the SDKs. Expect improvements. For developers on OpenAI or Google that have been using Stainless-generated SDKs, no urgency — but it's worth understanding the longer-term direction.

Bottom Line

Buying the company that generates your competitor's SDKs is an unusual move. It is also a clear statement about where Anthropic believes the next frontier of competition lies: not in raw model capability, where the gaps are narrowing, but in the developer experience layer that determines which lab actually gets built on. The Stainless acquisition is Anthropic's bet that the lab with the best agents and the cleanest tools wins.