Sourced*
Start free
Dashboard
Migration Affected by the Stainless acquisition? Import a public repo or upload files to start the Sourced migration. Migrate from Stainless to Sourced→

Stainless migration offer

Moving off Stainless? Get 50% off Launch and Scale for 6 months.

Per Stainless's own announcement, new signups, projects, and SDKs stopped the day the post published, as the company winds down its hosted SDK generator and Docs Platform on its way into Anthropic. Your OpenAPI spec, stainless.yml, and generated repos stay yours either way. For teams making the move this quarter, Sourced is offering 50% off Launch and Scale for 6 months — code STAINLESS50 at checkout.

Start Stainless migration→

Unlimited previews, up to 2 hosted docs review sites, and 1 hosted MCP server. No credit card required.

  • Offer50% off, 6 months
  • CodeSTAINLESS50
  • PlansLaunch + Scale
  • ImportGitHub or upload

02Stainless compatibility

Built to preserve Stainless migration intent.

Sourced reads stainless.yml as the contract for TypeScript/Python SDK previews, package metadata, auth env vars, and docs dependencies, then reports gaps before anything is published.

Why Sourced can make that claim

Sourced has converted thousands of OpenAPI schemas and Stainless-style config shapes to harden the converter around maximum compatibility. The migration path starts from the files Stainless customers already own, treats stainless.yml as the contract, generates SDK/docs previews, and reports every compatibility gap before anything is published.

  • Stainless inputs are treated as the contractSourced reads OpenAPI plus stainless.yml and preserves the migration-critical fields: package names, resources, subresources, method names, auth environment variables, production repo settings, README example intent, and docs/MCP metadata.
  • SDK compatibility is checked before publishingSourced generates TypeScript and Python SDK previews, then reports generated method coverage, skipped methods, constructor/auth shape, package metadata, error behavior, pagination, multipart, streaming, and other runtime review points before any registry write.
  • Docs compatibility is part of the same conversionSourced scans Stainless Docs Platform dependencies, hosted SDKJSON/API usage, Astro/Starlight setup, docs routes, redirects, custom-domain requirements, generated reference pages, sitemap, and llms.txt as part of the migration path.
  • Drift is reported instead of hiddenIf stainless.yml references a method missing from OpenAPI, or docs still depend on hosted Stainless reference data, Sourced keeps that in the compatibility report so teams can fix the source contract before customers see a changed SDK or docs site.
Schema conversions1,000s

Sourced's converter has been hardened across thousands of OpenAPI schema shapes and Stainless-style config patterns.

SDK method parity0 missing

In production Stainless migration QA, Sourced generated every configured TypeScript and Python method that was present in OpenAPI.

Parsed surface38 ops

A real messaging API migration parsed 38 OpenAPI operations, 12 schemas, and 34 SDK methods per language.

Migration artifacts6 outputs

Each run produces report, logs, TypeScript SDK, Python SDK, docs preview, and artifact manifest for review before publishing.

01Details

What's changing at Stainless

01

Stainless announced it is joining Anthropic, with more Anthropic-aligned work going forward.

02

New signups, projects, and SDKs stopped the day that announcement published, per Stainless's own post.

03

Existing Stainless customers continue to have access to the dashboard, generation, and hosted Docs Platform, plus an official transition documentation set at app.stainless.com.

04

None of this touches what you already own: your OpenAPI spec, stainless.yml, and generated SDK and docs repos stay yours no matter which generator produced them.

02Details

The offer

01

50% off Sourced Launch ($99/mo) and Scale ($349/mo) for 6 months — code STAINLESS50 at checkout.

02

For teams migrating off Stainless. Apply the code on the Sourced billing page when you subscribe or upgrade.

03

SDK languages today: TypeScript and Python, fully managed — generation, docs hosting, and compatibility reports. Other languages are on the roadmap and not shipped yet, so plan the migration around what's live now.

04

Start free first: run the compatibility report and preview the generated SDK and docs before spending anything, then apply the code when you upgrade.

03Switching path

The four-step migration this offer is for

Reversible — nothing reaches a customer until you approve the compatibility report.

  1. 01

    Import or upload OpenAPI + stainless.yml

    Paste a public GitHub repo URL for a one-click import, or upload the files manually. Sourced reads stainless.yml as the migration contract and preserves package names, auth env vars, and resource shapes.

  2. 02

    Read the compatibility report

    Sourced diffs the generated TypeScript and Python SDK against your live Stainless package — method coverage, error classes, pagination, and README examples, before anything changes.

  3. 03

    Preview docs and SDK output

    A hosted docs preview (with llms.txt) and downloadable TypeScript and Python SDK packages, at a private URL. Customers see nothing yet.

  4. 04

    Publish on your timeline, then apply the code

    When the report is clean, prepare repo-sync and docs cutover checks. Apply STAINLESS50 on the Sourced billing page when you upgrade to Launch or Scale — 50% off for 6 months.

Start Stainless migration→ Migration checklist