LlamaIndex Begins Stainless Exit, Seeking to Preserve SDK Interfaces
The hard part is not finding another generator. It is retaining the methods, types and behavior LlamaParse developers already use.
Loading page…
The hard part is not finding another generator. It is retaining the methods, types and behavior LlamaParse developers already use.
Listen to this story
Anthropic’s May 18 acquisition of Stainless—and Stainless’s move away from hosted products—has turned LlamaIndex’s SDK generator into a compatibility problem. For LlamaParse, LlamaIndex is starting a migration aimed at preserving the public interfaces developers already use, not merely reproducing generated code. Those interfaces include resource and method structures, names, types, parameters, pagination, return behavior, and exceptions.
Stainless powered every official Anthropic SDK from the API’s earliest days.
Hundreds of companies used Stainless for SDKs, command-line tools, and MCP servers.
LlamaIndex must preserve language-specific conventions, resource structures, types, parameters, pagination, and exception behavior.
LlamaIndex is migrating away from Stainless after Anthropic acquired the developer-tooling company and Stainless began winding down its hosted products. The immediate task is not simply replacing a code generator: LlamaIndex says it wants to preserve the SDK interfaces used by developers of its LlamaParse product.
Anthropic announced the acquisition on May 18. It said Stainless had powered every official Anthropic SDK since the earliest days of its API, while hundreds of companies relied on the company for SDKs, command-line tools and MCP servers, which are connectors that let agents and software reach external tools and data.
That workflow did more than produce functional code, according to LlamaIndex. Stainless provided a layer between the raw OpenAPI schema and the public SDK surface, allowing the company to shape libraries around the conventions developers expect in each programming language.
LlamaIndex says it would still choose Stainless again. But its transition illustrates a less visible cost of automation: once developers build against generated clients, changing the machinery behind them can become a compatibility project. Its stated goal is a generation pipeline it can operate for the long term without disrupting users’ existing interfaces.
Loading discussion...
Make your case
A view to debateGenerated SDKs can become a product dependency, not merely a build tool.
Explain what control customers should retain.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.