AiMatch

Octri.dev

Octri turns API specifications into editable documentation, SDKs, MCP tools, and production monitoring. API and developer-platform teams use it to publish and keep these outputs aligned to one spec.

One of 137 tools in Developer Tools

Visit Octri.dev Compare alternatives Own this tool? Claim it
Octri.dev screenshot

Who it's for

  • API platform teams that maintain OpenAPI, Swagger, Postman, or AsyncAPI definitions and need documentation and SDKs from the same source.
  • Developer teams publishing client libraries in one or more of Octri's supported languages and registries.
  • Engineering teams that want production telemetry from generated SDKs or a standalone backend monitoring package.

How it fits your workflow

Upload a supported API definition or connect a GitHub repository. Octri normalizes supported inputs to OpenAPI 3.1 and generates endpoint documentation, SDKs, an MCP server, and monitoring products.

Review and edit the generated docs, configure SDK conventions and languages, and enable the products you plan to use. Monitoring can run through generated SDK telemetry or a standalone package; the MCP server exposes documentation tools and callable endpoint tools.

When the spec changes, review the resulting draft and diff. Approve the changes to publish new SDK versions and update the connected outputs.

Pricing

Free: Free plan at $0 per month, with 50 API endpoints, 1 SDK language, 100 one-time AI credits, 100 MB monthly monitoring ingress, custom domain, GitHub sync, and registry auto-publish. Additional SDK languages are listed at $50 per month each; annual billing is advertised as saving 15%.

Free

$0/mo

  • · 50 API endpoints
  • · 1 SDK language included
  • · 100 one-time AI credits
  • · 100 MB monthly monitoring ingress

Starter

$49/mo + tax

  • · 100 API endpoints
  • · 2 SDK languages included
  • · 1,000 AI credits per month
  • · 1 GB monthly monitoring ingress

Growth

$99/mo + tax

  • · 300 API endpoints
  • · 4 SDK languages included
  • · 2,500 AI credits per month
  • · 5 GB monthly monitoring ingress

Business

$249/mo + tax

  • · 600 API endpoints
  • · All 10 SDK languages included
  • · 5,000 AI credits per month
  • · 20 GB monthly monitoring ingress

Enterprise

Custom

  • · Unlimited scale and custom allowances
  • · Custom AI credits and monitoring ingress
  • · SSO / SAML
  • · Dedicated support

Prices checked on Oct 4, 2026 from the vendor's site. They can change; confirm before you buy.

Key features

API documentation generation
Generates endpoint reference pages from a spec, including parameter tables, response schemas, and SDK request examples. Teams can edit the generated docs, add MDX guides, and publish them to a custom domain.
SDK generation and publishing
Generates client libraries in TypeScript, Python, Go, Java, Dart, Ruby, PHP, Rust, Swift, and Kotlin. Teams can configure language-specific conventions, exclude endpoints, add custom hooks, and auto-publish to registries.
Production monitoring
Collects structured logs, grouped issues, traces, service maps, N+1 query findings, synthetic uptime checks, and alerts. Monitoring can be enabled through generated SDK telemetry or a standalone backend package.
MCP server
Makes API documentation available through documentation tools and exposes callable tools for API endpoints to MCP clients, including Claude and Cursor. SDK Studio exclusions can also determine which endpoints are offered as agent tools.
OpenAPI spec audit
Scores a public spec or uploaded JSON/YAML spec against rules used by SDK Studio, including checks for schemas, path parameters, operation IDs, server URLs, authentication descriptions, and request bodies.
Spec-change review
A spec change produces a draft and a diff for approval; new SDK versions are published after approval. Documentation edits are stored per page, and regeneration affects endpoints that changed.

Works with

  • GitHub
  • SDK registries
  • MCP clients
  • Postman and AsyncAPI

Limitations to know

  • The Free plan is limited to 50 API endpoints and includes 1 SDK language; the listed endpoint allowances increase by plan, while Enterprise is described as unlimited.
  • Custom SDK code and components are listed for Growth and above, not Free or Starter.
  • Versioning is listed for Growth and above; white-labeling and SDK CDN hosting are listed for Business and above.
  • Self-hosting the generator and documentation renderer is limited to Enterprise plans.
  • Monitoring ingress is capped by plan: 100 MB on Free, 1 GB on Starter, 5 GB on Growth, and 20 GB on Business; Enterprise is custom.

Alternatives to consider

  • Theneo

    Choose it if you need a developer portal with changelogs, private customer portals, and real-time collaboration among engineering, writing, and product teams.

Compare Octri.dev side by side

Getting started

npx @octri/mcp
  1. Upload a spec file or connect a GitHub repository; inputs can be OpenAPI, Swagger, Postman, or AsyncAPI in JSON or YAML.
  2. Review and edit the generated endpoint documentation, then publish it.
  3. Configure SDK languages and conventions, and enable monitoring or the MCP server as needed.
  4. Review and approve a draft and diff after spec changes before new SDK versions are published.

Frequently asked questions

Do I have to use all four products?

No. The page says plans are not per-product, so a team can leave a product switched off and turn it on later without redoing existing setup.

What does monitoring inside the SDK mean?

Generated SDKs can report production errors tagged with the SDK version, language, and method that failed. The resulting telemetry counts toward the plan's monthly ingress allowance.

Can I edit the generated docs and SDKs?

Yes. Documentation changes are stored per page, and a new spec revision only disturbs endpoints that changed. Custom SDK code is available on Growth and above.

What happens when my spec changes?

A rebuild produces a draft and a diff. New SDK versions reach registries after the team approves the changes.

Is my spec or telemetry data used to train models?

The page says no.

Can I self-host?

Enterprise plans can run the generator and documentation renderer in the team's own infrastructure.

How hard is it to migrate from another docs or SDK tool?

The importer rebuilds the existing structure from the configuration file. The page says a normal documentation site migration takes most of a day, while custom components or bespoke pages may take additional work.