Anthropic buys Stainless, shifts SDK power
- Anthropic said on May 18 it acquired Stainless, bringing in-house the SDK generation system used by Anthropic and by rivals including OpenAI and Google. - Stainless had powered every official Anthropic SDK since the API’s early days, while TechCrunch reported Anthropic will wind down hosted Stainless products. - QuickSilver Pro says developers can switch by changing a base URL and key, using an OpenAI-compatible API across multiple models.
Anthropic said on May 18 that it had acquired Stainless, the developer-tools startup behind SDK automation used by OpenAI, Google and Cloudflare, bringing a piece of AI plumbing in-house as model companies compete for developers. Anthropic said Stainless had powered every official Anthropic SDK since the early days of its API, and described the company as a provider of SDK, CLI and Model Context Protocol server tooling. TechCrunch reported that Anthropic will wind down all hosted Stainless products, including its SDK generator, while existing customers keep rights to the SDKs they have already generated. The deal matters because SDKs are the layer many developers actually touch. Stainless turns an API specification into language-specific libraries in Python, TypeScript, Go, Java and Kotlin, and updates them as APIs change, reducing the manual work of keeping client libraries current. Katelyn Lesse, Anthropic’s head of platform engineering, said Stainless had shaped how developers experience the Claude API “since the start.” (anthropic.com) ### Why does buying an SDK company matter more than it sounds? Stainless was not a consumer brand, but it sat close to the integration path for major AI and cloud companies. TechCrunch reported that customers included OpenAI, Google and Cloudflare, and said the software was also valuable to companies building agents that connect to outside systems. That makes the acquisition less about a feature add than about control over how APIs become production-ready libraries. (anthropic.com) Alex Rattray, Stainless’s founder and chief executive, said in Anthropic’s announcement that he started the company because “SDKs deserve as much care as the APIs they wrap.” Anthropic said hundreds of companies rely on Stainless to generate SDKs, CLIs and MCP servers. Forbes described the move as cutting off rivals’ access to hosted Stainless products after the acquisition. ### What exactly is Anthropic taking off the market? (techcrunch.com) TechCrunch reported that Anthropic will wind down all hosted Stainless products. Anthropic told the outlet that customers will still own the SDKs they generated and have full rights to modify and extend them. In practice, that means previously generated libraries do not disappear, but the hosted pipeline that produced and maintained them is no longer a neutral vendor service. (anthropic.com) Anthropic said Stainless had also worked on MCP server tooling. Anthropic created the Model Context Protocol to let agents connect to external tools and data sources, so the acquisition also folds more of that connection layer into the Claude platform. ### Where does QuickSilver Pro fit into the same story? QuickSilver Pro is pushing from the opposite direction: not owning a tooling layer, but flattening model access into one key and one API shape. (techcrunch.com) Its website says developers can point the official OpenAI SDK at its base URL and use an OpenAI-compatible HTTP API for several top open-source models at prices about 20% below competing resellers. Its documentation says existing OpenAI integrations can switch with minimal or no changes. (anthropic.com) A social post cited in the briefing said QuickSilver Pro had attracted more than 1,000 developers in weeks by offering one OpenAI-compatible key across 12 frontier models at roughly 20% below market. I could verify the pricing and OpenAI-compatibility from QuickSilver Pro’s own materials, but not independently confirm the “1,000+ developers” figure beyond that cited post. ### Why are both moves aimed at the same choke point? (quicksilverpro.io) The common target is the developer surface. Anthropic is moving upstream into SDK generation and agent connectivity tooling; QuickSilver Pro is moving downstream into the API gateway that lets developers swap models without rewriting code. Both approaches reduce friction at the exact point where teams choose defaults: which client library, which endpoint, which key, which pricing table. That is an inference drawn from the products’ stated functions and positioning. (quicksilverpro.io) On May 19, the next concrete step is operational rather than regulatory: Anthropic is integrating the Stainless team and winding down hosted Stainless products, while QuickSilver Pro continues marketing a base-URL-and-key swap for developers already using OpenAI-compatible clients. (anthropic.com)