---
title: "Contact"
url: https://typeship.dev/contact
---

# How to reach us.

Three channels, all going to the same small team. Pick by what the message is.

## Channels

- [hello@typeship.dev](mailto:hello@typeship.dev) — Anything at all: what typeship generates, whether it fits your spec, pricing and Enterprise, partnerships, press, and security reports.

- [github.com/typeship-ax](https://github.com/typeship-ax) — Bugs in a generated package. The TypeScript, Python, and Go clients are public repositories with issues open. Include a failing case if you have one.

- [submit_docs_feedback](https://typeship.dev/docs/typeship-api/mcp) — A documentation page that is wrong, missing, or unclear. It is a tool on typeship's MCP server, it needs no API key, and it takes the page and what you expected. An agent that hits a bad page can file it without asking anyone.

## Before you write

For anything about what typeship generates from a particular spec, the fastest answer is usually to run it. The generator on the home page takes a spec URL or an upload, needs no account, and covers the first 25 operations. If it produces something wrong, that output is the best possible attachment.

For questions the documentation could answer, /llms.txt is the whole site in one fetch and /docs is the same thing for people. The reference for every API operation is generated from the spec, so it is never behind it.

## The company

typeship inc publishes typeship.dev, the console, the typeship API, and the packages typeship generates. What the service may be used for is in the terms of service; what is collected and why is in 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)