Stainless announced it is joining Anthropic. Direction: more Anthropic-aligned work going forward.
Industry
Anthropic and Stainless: what changes for your SDK and docs.
Stainless joining Anthropic is a planning moment for any team that ships Stainless-generated SDKs and docs. This page is the practical lens — what changes, what doesn't, the inventory to take, and a reversible migration plan if your team decides to move.
Completely free for 30 days. No credit card required.
01Details
What we know
Existing Stainless customers continue to have access to the dashboard, generation, and hosted Docs Platform.
An official transition documentation set exists at app.stainless.com for affected customers.
02Details
What doesn't change
You own your OpenAPI spec, stainless.yml, SDK repos, and the docs repo.
Customers of your SDKs do not care which generator produced the code, only that the surface stays stable.
A migration is a workflow change for your team, not a customer-facing change.
03Inventory
The inventory to take this quarter
OpenAPI source and stainless.yml.
Every SDK repo and its npm / PyPI publish settings.
Docs repo and any custom domain.
README example endpoints, MCP host settings.
Any team-internal scripts or CI that integrates with Stainless's hosted APIs.
04Migration
What a reversible migration looks like
Upload OpenAPI + stainless.yml to Bloom.
Read the compatibility report against your existing Stainless-generated SDK.
Preview docs and SDK output at a private URL.
Repo-sync and cut over on your timeline; keep Stainless live during cutover.