---
title: "About"
url: https://typeship.dev/about
---

# The Agent Experience company.

typeship makes APIs agent-friendly. We read your OpenAPI or GraphQL spec and generate the SDKs, the CLI, and the MCP server your API needs, then keep them current as the spec changes.

## What we build

typeship reads an API description and writes the client side of it. Swagger 2.0, OpenAPI 3.0 and 3.1, and GraphQL schemas all work.

Out of it comes a typed SDK in TypeScript, Python, or Go with no runtime dependencies, a CLI with one command per operation, and an MCP server with one tool per operation. Auth, pagination, retries, errors, validation, webhooks, and streaming all come from the spec.

Link a project to where the spec lives and typeship watches it. On a change it regenerates and opens a pull request per language, with a changelog and a semver verdict on the diff.

## Who it is for

API producers who already ship something and know it is incomplete. There is usually a spec, a hand-written client or two that have drifted from it, and a docs site meant for people to read.

What is missing is the rest: a client that matches the spec today, a CLI a script can drive, an MCP server that exists at all. typeship rounds out the developer experience and the agent experience together, without staffing a codegen project to do it.

## Agent experience

Agent experience is a narrower question than developer experience, and an easier one to check. Can software that has never seen your API find it, read what it does, get a credential, make a correct call, and understand the error when it gets one wrong?

Most APIs fail somewhere early in that list. Everything an agent needs usually exists, but only in a form built for people: docs that render in a browser, a client library a version behind the spec, an error that arrives as HTML. typeship publishes the same facts in a form software can read, and regenerates them so they stay true.

## How we work

The spec is the only input. typeship never asks you to describe your API twice. Where a spec is wrong or thin, you patch it at a JSON Pointer path, and the patch survives the next regeneration.

The output belongs to you. Generated packages are MIT-licensed source files in your repository, with no runtime dependency on typeship and nothing phoning home. If you stop paying, they keep working.

We run typeship on typeship. The TypeScript SDK, the CLI, and the MCP server we publish are generated from our own OpenAPI document by the same engine you run.

## Getting started

The generator on the home page needs no account: paste a spec, pick a language, download the package. Free covers one platform and the first 25 operations of a spec. Pro is $299 per platform per month, counting each SDK language as a platform. Enterprise is priced by contract, and the pricing page has the full breakdown.

If you are an agent: /agents.md is written for you and is a better place to start than this page.

## The company

typeship inc publishes typeship.dev, the console, the typeship API, and the packages typeship generates. Email hello@typeship.dev, or see the contact page for the other channels. Use of all of it is governed by the terms of service and the privacy policy.

## Elsewhere

- [https://typeship.dev/llms.txt](https://typeship.dev/llms.txt) — every page on this site
- [https://typeship.dev/agents.md](https://typeship.dev/agents.md) — the runbook, written to agents
- [https://typeship.dev/legal/terms](https://typeship.dev/legal/terms) and [https://typeship.dev/legal/privacy](https://typeship.dev/legal/privacy)