If your SDK pipeline just lost its host, freeze the contract before you migrate.

Anthropic announced its Stainless acquisition on May 18, 2026. Stainless says hosted products, including the SDK generator, are winding down and that new signups, projects, and SDKs are no longer available. The practical question for API teams is simple: can you still ship SDK updates, docs, examples, and MCP connectors without breaking customers?

send SDK scope snapshot $199 all payment links

trigger: Stainless wind-down
first buy: $199 snapshot
patch sprint: from $799
boundary: authorized repos only

sdk-continuity.plan

$ inspect sdk-pipeline
source: openapi.yaml
outputs: typescript python go docs mcp
release: github actions + npm/pypi
risk: generator dependency
docs: examples/auth drift

$ deliver snapshot
contract freeze map
language parity table
replacement path
first patch order

why now

This is a current operations problem, not a generic migration page.

Anthropic's announcement says Stainless generates SDKs, CLIs, and MCP servers from API specs across TypeScript, Python, Go, Java, and more. Stainless' own transition note says hosted Stainless products are winding down and directs customers to transition from Stainless-managed products to other options. Any API company that relies on a hosted generation workflow needs a short continuity pass before the next public API change.

The same week, AWS described AgentCore Payments handling x402 negotiation for agents accessing paid APIs, MCP servers, web content, and other agents. That makes API surfaces, SDKs, MCP connectors, payment docs, and observability part of the same launch path.

snapshot deliverables

What the $199 continuity snapshot gives a founder.

contract

Spec freeze map

OpenAPI location, transforms, ignored routes, auth schemes, pagination, webhooks, examples, generated docs, and release blockers.

sdk

Language parity table

Which generated SDKs exist, which are customer-critical, where tests live, and which release channels are exposed.

mcp

Connector continuity

Whether MCP server output, tool names, auth scopes, and docs can survive the generator move without changing buyer workflows.

Release proof

GitHub Actions, package publishing, changelog, generated-code diff policy, and rollback path before the next SDK release.

vendors

Migration options

A pragmatic path across hosted generators, open-source generators, or a thin custom pipeline, based on the repo rather than hype.

order

Patch order

The smallest first fixes: spec cleanup, examples, tests, auth docs, package metadata, and customer-facing migration note.

patch sprint

The $799 sprint is for teams that need a working replacement path, not just a memo.

A patch sprint is scoped after the snapshot. Typical sprint work: move one language SDK to a new generator, add CI diff checks, repair OpenAPI examples, generate a minimal MCP server proof, write a migration note, or make package metadata ready for the next release. The sprint stays inside an authorized repo and avoids customer data, production secrets, wallet keys, and paid calls unless test fixtures are explicitly provided.

scope examples:
  - OpenAPI cleanup + generator config
  - TypeScript SDK parity proof
  - Python package release checklist
  - MCP tool-name and auth-scope pass
  - docs/examples migration note

sources

The trigger is dated and public.

scope snapshot

2026-05-18

Anthropic acquisition note

Anthropic announced the Stainless acquisition and described Stainless' SDK, CLI, and MCP server tooling role.

open source

2026-05-18

Stainless transition note

Stainless says hosted products, including its SDK generator, are winding down and points customers to transition steps.

open source

2026-05-07

AgentCore Payments

AWS describes agents paying for APIs, MCP servers, web content, and other agents through managed payment infrastructure.

open source

contact

Private first

Send one repo or spec URL, current SDK languages, and the must-not-break customer flow. Findings stay private unless both sides agree.

send scope