Superpower Daily

Superpower Daily

Your reading space

Sign in
Future of Life Institute Convenes Bipartisan AI Oversight Push...Apple Releases macOS 27 With a Siri That Can Read Your ScreenAudit Finds No SWE-bench Pro Leaderboard Score Has a Complete P...Emergence Finds AI Agents Invent Opaque Shared Dialects in Coop...Salesforce Connects Gemini Enterprise to Its Data Without Custo...Meta Launches Meta One Subscriptions for More AI Across Its AppsFuture of Life Institute Convenes Bipartisan AI Oversight Push...Apple Releases macOS 27 With a Siri That Can Read Your ScreenAudit Finds No SWE-bench Pro Leaderboard Score Has a Complete P...Emergence Finds AI Agents Invent Opaque Shared Dialects in Coop...Salesforce Connects Gemini Enterprise to Its Data Without Custo...Meta Launches Meta One Subscriptions for More AI Across Its Apps
Swipe

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.

By 2 min read
LlamaIndex Begins Stainless Exit, Seeking to Preserve SDK Interfaces
LlamaIndex Begins Stainless Exit, Seeking to Preserve SDK Interfaces

Listen to this story

The audio brief

About 1:35
0:001:35
Read transcript
LlamaIndex is beginning a migration away from Stainless, after Anthropic acquired the developer-tooling company and Stainless started winding down its hosted products. The immediate challenge is LlamaParse, LlamaIndex’s document-parsing product: its developers already depend on software development kits generated through Stainless, and LlamaIndex wants to move the machinery without changing the interface those developers use. That interface is broader than a collection of generated files. Stainless sat between the raw OpenAPI description of an API and the public libraries built on top of it. It helped shape resource and method structures, names, types, parameters, pagination, returned data, and exception behavior around the conventions of each programming language. That matters because application code is written against those details. A replacement generator could produce code that works while still breaking imports, method calls, type expectations, or error handling. LlamaIndex says it would choose Stainless again, but the company’s transition shows the long-term obligation created by generated tooling: once customers build against a generated client, its surface becomes a product to maintain. Anthropic said on May 18, 2026, that Stainless’s team was joining Anthropic. It also said Stainless had powered every official Anthropic software development kit from the API’s earliest days, while hundreds of companies used it for kits, command-line tools, and connectors for agents and external data. The key thing to watch is whether LlamaIndex can operate a new generation pipeline internally while preserving the behavior its LlamaParse developers already rely on.

Story brief

3 key points

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...

  1. 01

    Stainless powered every official Anthropic SDK from the API’s earliest days.

  2. 02

    Hundreds of companies used Stainless for SDKs, command-line tools, and MCP servers.

  3. 03

    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.

The generator sat between the API and its users

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.

Why another generator is not automatically a substitute

What the existing SDK surface includes

  • Methods and resource structures used in application code.
  • Model names, namespaces, types and parameter names.
  • Behavior around pagination, returned data and exceptions.

A transition period, not an open-ended service

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.

Sources

  1. anthropic.comAnthropic acquires Stainless
  2. llamaindex.aiAu Revoir, Stainless

Loading discussion...

Related coverage

Continue reading