Specless

Go from an OpenAPI spec to a working SDK, npm package, or API docs site in a few minutes.

You have an OpenAPI spec. You want a typed SDK, a private npm package, or hosted docs. Specless does that.

How it works

Drop in your spec

Upload an OpenAPI file (JSON or YAML) or paste a URL.

Pick your outputs

SDK repo, npm package, docs site - or all three.

Use it

Clone the repo, install the package, or share the docs link.

What you get

SDK repo

A git repo with typed client code generated from your spec. Supports TypeScript out of the box. Clone it, push to your own remote, modify whatever you want.

npm package

A private registry package you can install with pnpm add @your-org/api-client. Auto-published when you update your spec.

API docs

A hosted docs site with endpoint references, request/response examples, and auth info. Share the link with your team or make it public.

Supported specs

Both JSON and YAML work. If your spec validates with the OpenAPI tooling you already use, it will work here. Specless reads OpenAPI 3.0 and 3.1.

Swagger 2.0 files need to be converted first. There are free tools for that - we recommend swagger2openapi.

Project dashboard

After importing your spec, you land on the project dashboard. This is where you manage everything - trigger generation, check output status, grab links.

Each output is independent. Generate just the docs now and add the SDK later. Or do all three at once.

Specless tracks changes. Upload a new version of your spec (or let URL sync handle it) and your outputs regenerate automatically. SDKs get a new branch, docs update in place, npm packages publish a new version.

Your URLs and package names stay the same across updates. Nothing breaks for consumers.

Next steps

Importing your spec - how to upload or link your OpenAPI file
SDK generation - what the generated code looks like
API docs - hosting and customizing your docs site

Getting started