APIs should work for agents, too.

Point Typeship at your API spec and choose what to generate: a CLI, an MCP server, or a native SDK.

Each interface feels hand-built for its audience. Developers get familiar commands and native clients; agents get structured tools, actionable errors, and the context they need to make a correct call.

When the API changes, Typeship regenerates each target, tests it, checks compatibility, and opens a pull request with the changelog and required version bump.

A Spec makes a product programmable. Purpose-built interfaces make it accessible. Developers expect native clients and commands; agents need structured tools, useful context, and errors they can recover from.

Typeship turns the API you already have into those interfaces and keeps them aligned as your product changes. Developers and agents can use more of your product without your team building and maintaining every client by hand.

Your Spec remains the source of truth. Typeship adds only what the contract cannot know, such as package identity, repository destination, documentation, and runtime preferences. Spec patches let you correct or enrich the generated surface without forking the source spec.

The generated source belongs to you, lives in repositories you control, and has no runtime dependency on Typeship. You review every update before it lands and publish under your own name.

We use Typeship to build Typeship. Our public CLI, MCP server, and TypeScript SDK are generated from the Typeship API with the same engine customers use.

Typeship Inc builds and operates typeship.dev, the Typeship API, and the public Typeship CLI, MCP server, and SDKs. Reach us at hello@typeship.dev, through our public GitHub repositories, or through the documentation feedback tool in the Typeship MCP server.