Generate SDKs, MCPs, Docs from OpenAPI Spec

Upload an OpenAPI 3.0 or 3.1 file to generate production-ready Code, readable docs, and a read-only API Reference for your API team.

Readable documentation with SDK configuration and resource navigation
Docs1 / 6
Generated TypeScript SDK modules, schemas, and typed request and response models
SDK2 / 6
Petstore API reference with grouped operations, HTTP methods, and response codes
API Reference3 / 6
Interactive Scalar API documentation with parameters, request examples, and responses
Scalar4 / 6
Hosted MCP server with available tools and private connection settings
MCP5 / 6
Generated Postman collection with downloadable requests and compatibility notes
Postman6 / 6

One spec. A complete API workspace.

Upload once to generate docs, SDK, and API reference. Export OpenAPI, Postman, MCP, and Scalar from your workspace.

Upload an API specification

restoring
Your specification
Specification details appear after validation
  1. Upload: pending
  2. Validate: pending
  3. Generate: pending
  4. Save: pending
  5. Ready: pending

Live activity

    Restoring progress

    Keep this page open until the upload is accepted.

    OpenAPI3.0 / 3.1

    Supported contract versions for uploads.

    SDK packagenpm-ready

    Output is shaped for package publishing workflows.

    AI docsllms.txt

    Generated docs are available for LLM discovery.

    PreviewDocs / SDK / Scalar / MCP

    Generated sessions expose docs, focused SDK modules, API calls, and MCP tool testing.

    [01 / 05 / Workflow]

    From OpenAPI upload to team-ready SDKs and docs

    A compact path from source contract to reviewable workspace, with package publishing called out alongside interactive MCP, Scalar, and Postman previews.

    01Upload OpenAPIDrop JSON or YAML
    02Generate SDK + docsBuild package-ready files
    03Edit and reviewWork in an editor-style view
    04Publish package (soon)npm or private registry

    [02 / 05 / Capabilities]

    Built for API teams shipping SDKs and docs together

    Keep generated files, rendered docs, AI docs, and upcoming release targets visible from one OpenAPI-centered workspace.

    01 / Upload

    Start from the OpenAPI contract your team already owns

    Drop OpenAPI 3.0/3.1, Swagger 2.0, or a Postman collection and open a workspace built around the source contract.

    02 / Generate

    Create production-ready SDK files and editable docs

    One upload produces browsable Docs, a structured TypeScript SDK, an interactive Scalar reference, and operation metadata.

    03 / Review

    Preview files and docs in an editor-style workspace

    Developers can inspect rendered docs, focused SDK modules, operation summaries, and test requests from the same workspace.

    04 / Package

    Generate MCP servers and Postman collections

    Preview MCP tools and validate inputs, or inspect the Postman/OpenAPI representation that complements the uploaded source.

    Available now

    Upload OpenAPI or a postman collection, generate docs and SDK files, preview code, use AI chat, and expose AI-readable docs through llms.txt.

    Soon: package publishing

    Create versioned SDK packages for npm, GitHub Packages, or private registries from the generated output.

    MCP tool workspace

    Open the MCP tab to select API operations, inspect runtime credential names, and validate tool input before connecting a client.

    [03 / 05 / Comparison]

    From one upload to a release-ready API workspace

    The root page makes SDK generation, docs review, AI readiness, and MCP output and planned package publishing clear from the first click.

    First action

    BeforeStart with a temporary upload
    API workspaceUpload a contract from the root page to open a generated workspace

    Generated output

    BeforeTemporary preview
    API workspaceDocs, SDK, Scalar, MCP, and a source-aware Postman/OpenAPI view

    Team workflow

    BeforeCopy generated files into separate tools
    API workspaceReview docs and SDK output in one editor-style workspace

    Release path

    BeforeManual versioning and publishing steps
    API workspacePlanned package publishing to npm or compatible registries with versioned releases

    MCP output

    BeforeBuild a custom MCP server after SDK generation
    API workspaceInteractive MCP tool preview with operation filters and input validation

    AI readiness

    BeforeDocs only written for humans
    API workspacellms.txt, llms-full.txt, and AI chat for generated docs

    [04 / 05 / FAQ]

    Answers before the first upload