Our Take
Anthropic just removed a shared utility from the AI lab supply chain—a defensible move that also signals how tight the infrastructure bottleneck has become.
Why it matters
SDK tooling is table stakes for agentic systems that need to call external APIs. By acquiring and closing Stainless, Anthropic gains internal control over developer friction while denying OpenAI and Google a tool they've relied on since 2022.
Do this week
If you use Stainless-generated SDKs: audit your API integration workflows this week and prepare to own SDK maintenance in-house, since the hosted generator shuts down.
Anthropic acquires Stainless and shuts the service down
Anthropic announced Monday it acquired Stainless, a New York-based startup founded in 2022 by former Stripe engineer Alex Rattray. The Information reported (per reporting, not company disclosure) that the deal valued the startup at more than $300 million. Anthropic has not disclosed deal terms.
Stainless built software that converts API specifications into production-ready SDKs across Python, TypeScript, Kotlin, Go, and Java. The platform automatically updated SDKs as APIs changed, eliminating manual maintenance work. The startup was backed by Sequoia Capital and Andreessen Horowitz.
The acquisition removes a widely-used tool from the market. Stainless SDKs power integrations at OpenAI, Google, Replicate, Runway, and Cloudflare. Anthropic says Stainless software has powered every official Anthropic SDK since its earliest API days.
Going forward, Anthropic will wind down all hosted Stainless products, including the SDK generator. Existing customers retain ownership of SDKs already generated and have full rights to modify and extend them. The public service ends.
Control over the infrastructure layer matters to agentic systems
Agentic AI requires agents to call external APIs reliably. SDKs are the glue between Claude and external services. If the SDK breaks or drifts from the API spec, the agent fails silently or produces hallucinated outputs.
By acquiring Stainless, Anthropic gains three advantages. First, it can optimize SDK generation and maintenance for Claude's specific agentic patterns—something a general-purpose tool cannot do. Second, it removes a shared utility that its competitors (OpenAI, Google) also depend on, creating asymmetry in development velocity. Third, it forces those competitors to either build SDK tooling in-house or work through slower, manual processes.
The move reflects tightening competition over developer moat. Anthropic has spent the past year pushing Claude into agents and enterprise deployments. Controlling the infrastructure that makes agents reliable is a defensible advantage.
Plan for SDK maintenance if you relied on Stainless
Organizations using Stainless-generated SDKs need to assess two risks: SDK drift and maintenance burden. The SDKs you've already generated remain yours. But if your APIs change, you no longer have automated SDK regeneration. You will need to maintain them manually or build your own generation pipeline.
If you are building agentic systems that call external APIs, assume you will own more of the tooling stack yourself. Evaluate whether to build internal SDK generation, adopt alternative open-source tools, or redesign your API surface to reduce the number of hand-maintained integrations.
For Anthropic customers, this is a signal: the company is betting on vertical integration for agent infrastructure. Expect tighter coupling between Claude, SDK tooling, and agent frameworks over the next 12 months.