Upload OpenAPI 3.0 or 3.1 (yaml or json) — Sourced infers a starter generator config from the spec.
How-to
Generate an SDK from OpenAPI without the glue work.
Upload an OpenAPI 3.x spec and Sourced generates a TypeScript and Python SDK preview, compares it to your live SDK, and gives you a launch report — before any package is published.
Unlimited previews. No credit card required.
01Details
Four steps
Sourced emits TypeScript and Python SDK previews with package.json, pyproject.toml, README, and a generation report.
If you supply a current SDK, Sourced diffs the public surface — methods, error classes, pagination, examples — and flags shapes to review.
Approve the report and Sourced prepares repo-sync, registry readiness, and docs-hosting readiness checks from the same spec.
02Outputs
What's in the generated SDK
Typed client class derived from your spec's operations and schemas.
Idiomatic method names per language (camelCase TS, snake_case Python).
Error classes for the standard HTTP statuses.
Auth options derived from your security schemes and env-var conventions.
README with a runnable client snippet using your spec's example endpoint.
03Details
Why Sourced is different from raw generators
Raw OpenAPI Generator templates produce code; Sourced adds the compatibility report and docs preview.
Sourced reads stainless.yml if you have one, so package names and existing customer-facing imports survive the migration.
Generation, docs, and publishing readiness stay in one workflow rather than three separate tools.
·Example output
A generation run shows the SDK artifact shape.
A local fixture run produced package.json, tsconfig.json, README.md, and src/index.ts.
A local fixture run produced pyproject.toml, README.md, typed package files, sync client, async client, errors, models, and utilities.
TypeScript and Python reports record package name, client name, base URL, resources, methods, skipped methods, and files.
Browser tests cover public pages, upload validation, signed-out blocking, generated links, failed runs, expired artifacts, publish-ready state, billing state, and the local HTTP worker artifact path.
| Example | Why it matters | Current result |
|---|---|---|
| TypeScript SDK report | Generated from OpenAPI plus config through the worker pipeline. | Package smoke, client APIAPI, 1 resource, 1 method, 0 skipped methods. |
| Python SDK report | Generated from the same input and includes sync plus async runtime surfaces. | Package smoke_api, clients APIAPI and AsyncAPIAPI, 13 emitted package files. |
| Run-state browser coverage | The dashboard is tested against the states users actually see after generation. | Generated artifacts, failed callbacks, expired artifacts, publish-ready releases, signed-out blocking, and billing readiness are covered. |