Generate production-ready TypeScript SDKs from OpenAPI

Automated publishing. Stays in sync forever.

From spec to typed SDK

Five OpenAPI documents, generated live by the same engine that publishes your package.

Three operations in, one configured client class out — parameters, bodies and responses all typed.

typed-client.openapi.json

Pet Store SDK0 files

No files generated yet

Select a file to view its contents

One client class, named after your API

Path and query parameters as typed arguments

Response bodies parsed into model classes

No runtime dependency beyond fetch

How it works

From OpenAPI spec to published npm package in three steps.

Connect your spec

Point code-forge.net at your OpenAPI document via a GitHub repository URL or a direct link.

Generate the SDK

The platform runs the-codegen-project CLI and produces a fully-typed TypeScript client SDK.

Publish automatically

The generated SDK is versioned and published to npm. Every spec change triggers a new release.

Your SDKs stay in sync. Automatically.

Connect your GitHub repository once. Every merge to your default branch that touches the OpenAPI spec triggers a regeneration and a new npm publish.

GitHub webhook triggers on every push
Diff-aware: only re-generates when the spec changes
Automatic semantic version bump on publish
Full generation log available in the platform dashboard

No lock-in

The SDK is yours, not ours

We generate plain TypeScript and publish it to your own npm scope, from your own token. There is no proprietary runtime to import and nothing to migrate off. If you ever stop paying us, the package keeps shipping and the code stays yours.

Published under your npm scope
Readable TypeScript, no hidden runtime
Source stays in your repo history