llms.txt
Compare with other sites' llms.txt files →# Octri
> Octri turns one OpenAPI spec into hosted API documentation, idiomatic SDKs in ten languages, an MCP server and production monitoring, on a live URL that rebuilds when the spec changes.
Octri is a hosted developer-experience platform for teams that own an OpenAPI
spec. You connect a spec file, a spec URL or a GitHub repository. Octri writes
reference documentation for every endpoint, generates client libraries, and
keeps both current as the spec changes.
The SDKs it generates can report their own production errors. Reporting ships
switched off, and the developer using the SDK turns it on with one setting.
From then on, when a client throws inside their application, the error reaches
you tagged with the SDK version, the language and the method that failed. That
is the capability that separates Octri from the other generators in this
category.
## Products
- [API Studio](https://octri.dev/api-studio): Documentation site generated from the spec, with a live request playground, full-text search, an ask-the-docs chat and an agent-readable index. Every page is editable and publishes to your own domain.
- [SDK Studio](https://octri.dev/sdk-studio): Client libraries in TypeScript, Python, Go, Java, Kotlin, Ruby, PHP, Rust, Swift and Dart, shaped in a visual studio and published to their native registries including npm, PyPI, Maven Central, crates.io, RubyGems, Packagist and pub.dev.
- [Monitoring](https://octri.dev/monitoring): Logs, issues, traces, performance, releases, uptime and alerts, covering both your API and the SDKs your users have installed. An event carries the error, the operation and the SDK version; request bodies, headers, cookies and IP addresses are never collected, and credentials and direct identifiers are redacted inside the SDK before anything is sent.
- [MCP Server](https://octri.dev/mcp): Seven documentation tools plus one executable tool per endpoint, generated from the same spec, for Claude, Cursor, VS Code and any other MCP client.
## From an OpenAPI spec
- [Free OpenAPI tools](https://octri.dev/free-tools): Index of the free browser tools for OpenAPI and Swagger specs, no account needed. Each tool has its own page, linked from the index.
- [Score an OpenAPI spec](https://octri.dev/openapi-audit): Free readiness audit: a spec scored out of 10 against the fourteen rules that decide whether a generated SDK is usable, with the whole rule catalogue published. No account, and the spec is not stored.
- [Public OpenAPI spec scores](https://octri.dev/openapi-audit#public-scores): Index of well-known public OpenAPI documents scored for SDK generation, each with its own page at /openapi-audit/<name> giving the score, the fourteen rule results and sample finding locations. Derived facts only; the documents themselves are not stored or served.
- [Validate an OpenAPI spec](https://octri.dev/openapi-parser): Free OpenAPI validator and parser: checks Swagger 2.0 and OpenAPI 3.0, 3.1 and 3.2 documents against their declared version with the line of each error, and bundles or dereferences $refs. Open source (Apache-2.0), runs in the browser.
- [Convert Swagger or Postman to OpenAPI](https://octri.dev/spec-converter): Free converter from Swagger 2.0, Postman collections, RAML, Insomnia, HAR and cURL to any OpenAPI 3.0, 3.1 or 3.2 release, or between OpenAPI versions. Lists every change and holds lossy ones for review. Open source, runs in the browser.
- [OpenAPI to TypeScript SDK](https://octri.dev/openapi-to-typescript-sdk): A typed TypeScript client from your OpenAPI spec, published to npm, with fetch or axios, auto-paging iterators and typed errors. Published to npm.
- [OpenAPI to Python SDK](https://octri.dev/openapi-to-python-sdk): A Python client from your OpenAPI spec, published to PyPI, with a blocking client, an asyncio client and a choice of pydantic, dataclass or TypedDict models. Published to PyPI.
- [OpenAPI to Go SDK](https://octri.dev/openapi-to-go-sdk): An idiomatic Go client from your OpenAPI spec, on the standard library, released by git tag so go get resolves it straight from your repository. Published to a git tag.
- [OpenAPI to Java SDK](https://octri.dev/openapi-to-java-sdk): A Java client from your OpenAPI spec, published to Maven Central under a groupId you control, with typed models and typed errors. Published to Maven Central.
- [OpenAPI to Kotlin SDK](https://octri.dev/openapi-to-kotlin-sdk): A Kotlin client from your OpenAPI spec, published to Maven Central, with data classes and a choice of OkHttp or Ktor with suspend functions. Published to Maven Central.
- [OpenAPI to Rust SDK](https://octri.dev/openapi-to-rust-sdk): A typed Rust crate from your OpenAPI spec, published to crates.io, with serde models, Result-based errors and pagination that stops when you say. Published to crates.io.
- [OpenAPI to PHP SDK](https://octri.dev/openapi-to-php-sdk): A PHP 8.2 client from your OpenAPI spec, released to Packagist for Composer, with readonly models, lazy pagination and no Composer dependencies. Published to Packagist.
- [OpenAPI to Ruby SDK](https://octri.dev/openapi-to-ruby-sdk): A Ruby gem from your OpenAPI spec, published to RubyGems, with keyword arguments, Enumerator pagination and no runtime dependencies. Published to RubyGems.
- [OpenAPI to Swift SDK](https://octri.dev/openapi-to-swift-sdk): A Swift package from your OpenAPI spec, with async/await, Codable models and AsyncThrowingStream pagination, released by git tag for Swift Package Manager. Published to a git tag.
- [OpenAPI to Dart SDK](https://octri.dev/openapi-to-dart-sdk): A Dart client from your OpenAPI spec, published to pub.dev, for Flutter mobile and desktop apps and Dart servers, with no runtime dependencies. Published to pub.dev.
- [OpenAPI to MCP server](https://octri.dev/openapi-to-mcp-server): How to turn a spec into an MCP server for Claude, Cursor and VS Code: the client config, the environment variables, and what an agent can read and call.
## Pricing
- [Plans and limits](https://octri.dev/pricing): Free, then $49, $79 and $249 per month, plus a custom Enterprise tier. Annual billing takes 15% off the base price. SDK languages beyond the bundled count are $50 per language per month.
## Comparisons
- [Compare Octri](https://octri.dev/compare): Every column side by side, checked 16 October 2026.
- [Octri vs Mintlify](https://octri.dev/compare/mintlify): A docs site plus first-party SDKs in ten languages from the same spec, and the monitoring those SDKs make possible.
- [Octri vs ReadMe](https://octri.dev/compare/readme): A docs site plus SDKs in up to 10 languages from the same spec, AI chat on every plan, and monitoring with a status page.
- [Octri vs Redocly](https://octri.dev/compare/redocly): A docs site written from your spec, SDKs in ten languages, a hosted MCP server and monitoring, with AI chat on every plan.
- [Octri vs Stoplight](https://octri.dev/compare/stoplight): A docs site written from your spec, SDKs in ten languages, a hosted MCP server and monitoring, with AI chat on every plan.
- [Octri vs GitBook](https://octri.dev/compare/gitbook): API docs written from your spec, plus SDKs in up to 10 languages, an MCP server that calls your API, and monitoring.
- [Octri vs Docusaurus](https://octri.dev/compare/docusaurus): API docs written from your spec and hosted for you, plus SDKs in ten languages, a hosted MCP server and monitoring.
- [Octri vs Scalar](https://octri.dev/compare/scalar): Docs, SDKs and a hosted MCP server, with all ten SDK languages in the plan and monitoring that Scalar does not offer.
- [Octri vs Fern](https://octri.dev/compare/fern): Docs and SDKs from one spec, any of ten languages on the free plan, and monitoring inside every client.
- [Octri vs Stainless](https://octri.dev/compare/stainless): Takes new projects, reads stainless.yml and adds monitoring inside every client it generates.
- [Octri vs APIMatic](https://octri.dev/compare/apimatic): SDKs in ten languages included in the plan, a docs site written from your spec, a hosted MCP server and monitoring.
- [Octri vs OpenAPI Generator](https://octri.dev/compare/openapi-generator): SDKs in ten languages with one feature set, regenerated and published for you, plus docs, MCP and monitoring.
- [Octri vs Speakeasy](https://octri.dev/compare/speakeasy): SDKs in ten languages with every price on the page, a docs site written from your spec, an MCP server and monitoring.
- [Octri vs liblab](https://octri.dev/compare/liblab): SDKs in ten languages with one feature set, a docs site written from your spec, a hosted MCP server and monitoring.
## Migration guides
- [Migrate to Octri](https://octri.dev/migrate): A guide for each tool, checked 25 October 2026.
- [Migrate from Stainless](https://octri.dev/migrate/stainless): Targets, package name, repository and method names from stainless.yml and your spec.
- [Migrate from Speakeasy](https://octri.dev/migrate/speakeasy): Languages, SDK name, package name and x-speakeasy extensions from workflow.yaml and gen.yaml.
- [Migrate from Fern](https://octri.dev/migrate/fern): SDK generators, package name, docs theme and the page list from the fern folder.
- [Migrate from liblab](https://octri.dev/migrate/liblab): Spec, languages, auth schemes and package name from liblab.config.json.
- [Migrate from Mintlify](https://octri.dev/migrate/mintlify): Name, theme, spec and the page list from docs.json or mint.json, plus your MDX by Pull from GitHub.
- [Migrate from ReadMe](https://octri.dev/migrate/readme): Your OpenAPI file and the Markdown that bi-directional sync keeps in Git.
- [Migrate from Redocly](https://octri.dev/migrate/redocly): Your bundled OpenAPI file, your Markdown in Git and the redirects in redocly.yaml.
- [Migrate from Scalar](https://octri.dev/migrate/scalar): The OpenAPI document from your Scalar registry or repository, and your Markdown and MDX guides.
- [Migrate from GitBook](https://octri.dev/migrate/gitbook): The OpenAPI file your API blocks read and the Markdown that Git Sync keeps in your repository.
- [Migrate from Stoplight](https://octri.dev/migrate/stoplight): The OpenAPI file and Markdown articles in the repository your Stoplight project syncs with.
- [Migrate from Docusaurus](https://octri.dev/migrate/docusaurus): The OpenAPI file your plugin reads, your MDX pages and the layout in sidebars.js.
- [Migrate from APIMatic](https://octri.dev/migrate/apimatic): The API definition your SDKs are built from and the Markdown guides in your portal.
- [Migrate from OpenAPI Generator](https://octri.dev/migrate/openapi-generator): The spec you pass to -i and the package names in your generator config.
## Documentation
- [Documentation](https://octri.dev/developers/guides/api-docs/overview): Guides for the docs site: structure, editing, theming and publishing.
- [SDK guides](https://octri.dev/developers/guides/sdks/overview): Generating, configuring and publishing client libraries.
- [MCP guides](https://octri.dev/developers/guides/mcp-server/overview): Connecting an MCP client and choosing which endpoints it may reach.
- [Monitoring guides](https://octri.dev/developers/guides/monitoring/overview): Wiring reporting, reading the workspace and setting alerts.
- [CLI guides](https://octri.dev/developers/guides/cli/overview): Driving specs, builds and artifacts from the command line.
## Writing
- [Blog](https://octri.dev/blog): Product news and writing on API documentation, SDKs and developer experience.
- [A Backslash Made Nginx and Node Disagree About an Admin Route](https://octri.dev/blog/backslash-nginx-node-admin-route): I sent 750 HTTP requests through 10 server configurations. One encoded backslash passed an Nginx guard and reached the Node handler it was meant to block. How URL normalization turns a reasonable access rule into a boundary that protects the wrong thing.
- [Why The Same JSON Request Can Mean Two Different Things](https://octri.dev/blog/same-json-two-meanings): I ran the same JSON through JavaScript and Go. One program read preview, the other read commit, and neither reported an error. How case-insensitive field matching, duplicate keys and re-serialization let a gateway and a backend disagree about what a request means.
- [What a Compromised VS Code Extension Could Do Before You Write a Line of Code](https://octri.dev/blog/compromised-vs-code-extension): We monitored 40 VS Code launches to see what extensions do in the background. Prettier and GitLens both activated on startup, and GitLens started helper processes that opened outbound connections. Neither showed signs of compromise. Both show how much trust an editor extension holds.
- [Can an AI agent actually integrate your API? Build an eval to find out](https://octri.dev/blog/agent-api-integration-evals): Give an agent a real task, an isolated sandbox and a result you can verify. Check the records and code the agent produces.
- [MCP or CLI? Run the same API workflow through both](https://octri.dev/blog/mcp-or-cli-api-workflows): Compare agent interfaces with the same task, permissions and outcome checks. Token counts mean little when one path does less work.
- [Your streaming API returned 200. Then it failed](https://octri.dev/blog/streaming-api-failures-after-200): An HTTP success status starts a stream; it does not prove the operation finished. Design explicit completion, interruption and recovery semantics.
- [Who built this SDK? Proving package provenance from spec to registry](https://octri.dev/blog/sdk-package-provenance): Connect a published SDK to its inputs and build workflow. Understand what trusted publishing and provenance establish, and what still needs review.
- [Your MCP server authenticates users. Does it preserve their permissions?](https://octri.dev/blog/mcp-user-permissions): Follow identity from MCP client to downstream API. Check token audiences, delegated credentials and tenant authorization at each boundary.
- [Your API response is eating the agent's context window](https://octri.dev/blog/api-response-context-budget): Design bounded responses that preserve useful facts. Filter, select and aggregate before large intermediate payloads enter an agent's context.
- [Your API examples compile. Do they actually work?](https://octri.dev/blog/executable-api-docs-examples): Run published examples against isolated fixtures and verify their outcomes. Compilation catches only one class of documentation failure.
- [202 Accepted is the beginning: designing APIs for long-running jobs](https://octri.dev/blog/long-running-api-jobs): Give asynchronous work an operation handle, explicit states and a documented recovery path. Acceptance is different from completion.
- [OpenAPI describes endpoints. Arazzo describes how to use them together](https://octri.dev/blog/arazzo-api-workflows): Describe dependencies, inputs and success conditions across API calls. Use Arazzo to make integration workflows explicit alongside OpenAPI.
- [One API spec, three audiences: stop maintaining three copies](https://octri.dev/blog/openapi-overlays-audiences): Derive public, partner and internal API descriptions from one base contract. Use repeatable overlays and validate each audience's output.
- [Your read-only MCP server can still carry a prompt injection](https://octri.dev/blog/read-only-mcp-prompt-injection): A tool can avoid writes while returning hostile instructions. Treat customer-controlled API content as untrusted data throughout an agent workflow.
- [One user, 200 API calls: rate limits when agents run in parallel](https://octri.dev/blog/agent-api-concurrency-limits): Coordinate agent fan-out against shared request and concurrency budgets. Queue work before dispatch instead of turning overload into a retry loop.
- [Your API's integer survived Python. JavaScript changed it](https://octri.dev/blog/json-integer-precision-sdks): A valid JSON number is not a portable precision guarantee. Protect identifiers and decimal amounts with explicit wire contracts and cross-language tests.
- [Works in Node.js. Breaks at the edge. Is your SDK portable?](https://octri.dev/blog/sdk-runtime-portability): Test SDK behavior against named runtimes and versions. Successful imports and familiar web APIs do not establish full runtime compatibility.
- [Follow one API request from the customer's SDK to your database](https://octri.dev/blog/sdk-to-database-tracing): Join request spans through context propagation. Understand retry attempts, database operations and trust boundaries without treating trace metadata as authorization.
- [Your monitoring bill grew. Your traffic didn't](https://octri.dev/blog/metric-cardinality-monitoring-cost): Extra metric dimensions can create far more time series without extra requests. Bound labels, understand overflow and retain the labels needed for diagnosis.
- [Where does an API key go when someone clicks Try it?](https://octri.dev/blog/api-playground-credential-path): Follow credentials through a documentation playground. Check browser storage, request destinations, proxy behavior and logs.
- [Your sandbox always succeeds. That's why integrations fail in production](https://octri.dev/blog/realistic-api-sandboxes): Design deterministic failure scenarios alongside happy paths. Give humans and agents a safe place to practice the behaviors production integrations need.
- [Measure your API docs by the first successful request](https://octri.dev/blog/api-docs-first-success): Follow onboarding from discovery to a verified result. Track completed steps and find where developers get stuck without collecting secrets or customer payloads.
- [Your OpenAPI spec can generate bug reports, too](https://octri.dev/blog/openapi-property-based-testing): Use schema-driven and stateful tests to explore API behavior. Preserve minimized failures and add business invariants the schema cannot express.
- [How to Choose an OpenAPI SDK Generator: 10 Questions to Ask](https://octri.dev/blog/choose-openapi-sdk-generator): Ten practical questions for evaluating generated SDKs: spec support, code quality, auth, errors, publishing, monitoring, and exit cost.
- [What Leaves Your Process: The Life of a Monitoring Event](https://octri.dev/blog/what-leaves-your-process): Every error your generated SDK reports crosses a line: out of your process, over the wire, into our disk. Here is what is inside it, the two scrubbers it passes on the way, where it sleeps, when it dies, and how you make us forget someone.
## Optional
- [Support](https://octri.dev/support): How to get help and what each plan includes.
- [Security](https://octri.dev/security): Data handling, encryption and disclosure policy.
- [Fair use](https://octri.dev/fair-use): What the metered limits mean in practice.
- [Subprocessors](https://octri.dev/subprocessors): Third parties that process customer data.
- [Data Processing Addendum](https://octri.dev/dpa): Pre-signed Article 28 DPA covering every product; nothing to countersign.
- [Monitoring DPA](https://octri.dev/dpa/monitoring): What telemetry contains, how it is redacted, where it is stored, when it expires and how a user is erased.
- [Terms](https://octri.dev/terms): Terms of service.
- [Privacy](https://octri.dev/privacy): Privacy policy.