Introducing Octri: API Docs and SDKs, Automatically

Shipping an API is easy. Keeping its documentation and client libraries in sync is the hard part. Octri closes that gap: point us at your OpenAPI spec and we generate documentation and ten production-ready SDKs, then keep both current on every push.

Why we built it

Teams waste days hand-writing docs and client wrappers that drift out of date the moment the API changes. We wanted a single source of truth: the spec.

Your OpenAPI document already describes every endpoint, parameter and response. Octri treats it as the contract and generates everything else from it.

What you get

• AI-written endpoint descriptions, examples, and error guides
• SDKs in TypeScript, Python, Go, Rust, and six more languages
• A hosted docs site with a live public URL from your first upload
• Automatic updates wired to your GitHub pushes

Supported languages

Language	Package registry	Status
TypeScript	npm	Stable
Python	PyPI	Stable
Go	Go modules	Stable
Rust	crates.io	Beta

Six more are documented in the SDK reference, including how each one installs and what its callers write.

A quick taste

Install the generated TypeScript SDK and call your API with full type safety:

import { Client } from "@acme/sdk";

const client = new Client({ apiKey: process.env.ACME_KEY });
const invoice = await client.invoices.create({ amount: 4200, currency: "usd" });
console.log(invoice.id);

You can also fetch it directly with curl while you explore:

curl https://api.acme.dev/v1/invoices -H "Authorization: Bearer $ACME_KEY"

Read the docs

Each part of the product has a guide that covers it properly:

• Documentation: what a spec turns into, and the guides you write alongside it
• SDKs: ten languages, and every setting that shapes them
• Monitoring: what your SDKs report back from production
• MCP server: your docs and endpoints as tools for coding agents

---

Ready to try it? Create your first project and upload a spec.