OpenAPI → SDK

SDKs that read like someone actually wrote them.

Point Osmundus at your OpenAPI spec and get back a typed TypeScript or Python SDK — deterministic, self-hosted, and yours to keep. No AI lab standing between you and your own developer tooling.

osmundus — terminal
$ osmundus generate --spec ./openapi.yaml --target all
✓ typescript-sdk/
✓ python-sdk/
$ osmundus import --stainless ./stainless.yml --spec ./openapi.yaml
✓ shape preserved — resource and method names unchanged

What you're actually getting

Five things, stated plainly — no feature you have to take on faith.

Typed end to end

Client, request params, response models, and errors — every resource, typed. Not just the happy path.

Deterministic output

Same spec in, byte-identical SDK out, every run. Nothing to diff, nothing to double-check.

Self-hosted

Run the generator yourself and read the code that produces your SDK. No vendor holding the only copy.

Stainless config import

Bring the config you already maintain. Osmundus keeps your SDK's resource and method names as they are.

Two languages, on purpose

TypeScript and Python — not Go, not Ruby, not Kotlin, not yet. We'd rather clear the quality bar on two languages than spread thin across seven. Osmundus is also a new company without years of production traffic behind it, so don't take the claims above on faith — generate against your own spec and read what comes out.

scope.json
typescript shipped
python shipped
go, kotlin, ruby not yet
The risk

Companies pay real money for hand-written-quality SDKs because writing and maintaining them by hand, across languages, is slow and repetitive work. Which means whoever generates them sits close to your core developer experience.

If that generator lives inside one company's roadmap — especially a model lab's — its priority next year depends on a decision you don't get a vote in.

A reorg, an acquisition, a change in focus: any of it can leave you rewriting a client library you never meant to touch again. Osmundus isn't a feature inside an AI lab's product line — it's the thing itself, and you can run it without us.

Questions worth asking

What does Osmundus actually generate?+

A typed client, typed request/response models, typed errors, auth handling, retries, and pagination helpers — in TypeScript and Python, from your OpenAPI spec.

Can I bring my existing Stainless config?+

Yes. osmundus import --stainless ./stainless.yml reads it and keeps your SDK's resource names, method names, and pagination pattern as they are. Anything it can't translate is reported as an explicit warning -- never silently dropped.

Do I have to self-host it?+

No — self-hosting is an option, not a requirement. Point the CLI at your spec and it runs wherever you run it; there's no hosted service you're required to route through.

Is Osmundus affiliated with Stainless or any model lab?+

No. Osmundus is an independent company. That independence — not being owned by a model lab or any single API vendor — is the whole point.

Run it against your real spec.

Free. No sales call required to see the output.

Generate your SDK
or run osmundus init to start from scratch