Octri Review (2026): Pricing, Features & Honest Verdict

TLDR

Octri turns one OpenAPI spec into a docs site, SDKs in ten languages, an MCP server and error monitoring. Pricing is fair and the legal pages are unusually candid, but the company is weeks old and its guides contradict its own data terms. Best for: small API teams. Price: from $49/mo, free plan yes. Rating: 7/10.

What is Octri?

We found Octri on Product Hunt, where it launched on 4 October 2026. It is a hosted platform for teams that publish an API. You upload an OpenAPI description and it generates four things: a documentation site, client libraries in ten languages, including TypeScript, Python, Go, Java, Rust and Swift, an MCP server that AI assistants can call, and a monitoring service that collects errors from those client libraries once they run in production.

The operator is Octri, LLC, a Delaware company, with Paddle as merchant of record. Its press page gives a founding date of September 2026, a team of 2 to 10 and no outside funding. So this is a very young product. We counted no testimonials and no customer logos on the site, and the changelog page in the docs was empty when we checked.

What Are Octri’s Key Features?

Docs generated from the spec

API Studio has an AI model write a first draft for each endpoint, which you then edit like a document. Edits are stored per page, so a new spec revision only disturbs the endpoints that changed. Each site gets a three-column reference, a try-it console, MDX guides and an Ask-the-docs chat. A custom domain is included on all plans, Free too, because the default subdomain is a random id. Octri’s own documentation site runs on the product, which is the one live sample we could inspect.

SDKs in ten languages

SDK Studio lets you rename methods, exclude internal endpoints and pick the HTTP engine per language. Builds carry typed models, retries, pagination and idempotency keys, and publish to npm, PyPI, Maven Central, crates.io, RubyGems, Packagist and pub.dev under your own registry accounts. Go and Swift ship by git tag. With GitHub sync, a spec change rebuilds a draft and shows a diff, and nothing reaches a registry until you approve it. The terms say generated SDKs are yours to modify, distribute and license, with no royalty.

Monitoring compiled into the SDK

This is the feature rivals lack. A generated client can report its own errors to an Octri dashboard, grouped into issues and tagged with the SDK version. The Monitoring Addendum lists what an event holds: error name, message and stack, the method, path and status, and a random event id. It says request and response bodies, headers, query strings and the caller’s IP address are never collected. Sixty-nine credential and identifier keys are redacted inside the client, then again at ingest.

We unpacked the standalone backend package, @octri/node 1.2.0, from npm to check. The code matches the claims: it has no hardcoded endpoint, sends nothing until init() is called, strips query strings and scrubs keys such as password, token, email and phone before posting. Telemetry is stored in a self-hosted analytics database on a server rented from OVH in the United Kingdom, and the Addendum says no AI provider receives it.

MCP server

One command, npx @octri/mcp, starts a server with seven documentation tools plus one callable tool per endpoint. Endpoints you exclude in SDK Studio vanish from the agent’s tool list too. The package is real: version 1.2.0 is on npm under an MIT licence, as are the ten monitoring runtimes on GitHub.

What Is It Like to Use Octri?

We did not sign up or generate an SDK, so this section follows the vendor’s docs. The flow is four steps: upload a spec or link a GitHub repository, review the AI draft, pick languages and build, then download a zip or publish. OpenAPI 3.0 and 3.1, Swagger 2.0 and AsyncAPI files are accepted and normalised to OpenAPI 3.1.

A free spec audit on the marketing site scores a spec out of 10 against fourteen published rules, with no signup. It is a sensible first stop, because the docs are blunt that a spec with missing operationIds produces ugly method names in all ten languages.

Turning on monitoring is a toggle on the project, followed by a rebuild and a new release. The docs stress that SDK versions published before the toggle never report, however long you wait. There is also a CLI for specs, builds, source maps and reading issues from a terminal.

Where Does Octri Fall Short?

The biggest problem is that Octri’s own pages disagree about its headline feature. The marketing copy says one switch on the project turns each installed client into a reporter, with nothing to add to anyone’s code. The Monitoring Addendum says the opposite: two switches, both off, and each generated client ships with logging disabled until the developer who installed the SDK enables it in their own code.

That difference decides if your customers’ applications send error reports to a third party by default. We searched the setup guides for the second switch, the consent function and the redaction flag, and none of them is documented there. No generated SDK is published for us to unpack, so we could not confirm which version is true. Read the documentation file bundled in a generated build before you publish one.

Other pages are stale. The redaction guide and the package’s bundled documentation say a user’s email is reported as set, while the 1.2.0 changelog and the code redact it. The setup guide says raw events are kept 30 days. The Fair Use Policy says 7 days on Free and up to 180 on Business. One page says monitoring overage is charged, another says it is only recorded today.

Octri is also unproven. The GitHub organisation has 12 public repositories with no stars, and @octri/node had 23 npm downloads in the week before launch. The security page admits there is no SOC 2 or ISO 27001 certification. The 99.9% availability figure is a target with no service credits, and liability is limited to twelve months of fees or $100, whichever is greater.

Plan gating is tighter than the feature grid suggests. Starter covers a single project, according to the Fair Use Policy. Versioning and custom code need Growth, white-label needs Business, and SSO and self-hosting are Enterprise only. Self-hosting covers the generator and the docs renderer, with no mention of monitoring.

How Much Does Octri Cost?

Paid plans start at $49 a month plus tax for Starter: one project, 2 SDK languages, 100 endpoints, 1,000 AI credits and 1 GB of monitoring. Growth is $99 for five projects, 4 languages, 300 endpoints, 2,500 credits and 5 GB. Business is $249 for all ten languages, 600 endpoints, 5,000 credits and 20 GB. The Free plan gives one project, one language, 50 endpoints, 100 one-time credits and 100 MB. Pricing is per organisation, with no seat fees.

Annual billing takes 15% off the plan price. The pricing script rounds this to $42, $84 and $212 a month, where an exact 15% would be $41.65, $84.15 and $211.65. Extra languages cost $50 a month each on Starter and Growth, and the terms say they get no annual discount. Do the sums first: Starter with two extra languages is $149 for 100 endpoints, while Growth includes four languages and 300 endpoints for $99.

One credit buys generated documentation for one endpoint or one Ask-the-docs answer. Credit packs cost $10 for 1,000, $45 for 5,000 and $160 for 20,000, and purchased credits never expire. The docs put a credit at about $0.002 of AI work, so packs sell at four to five times that. Monitoring past the allowance is accepted up to ten times the limit. No per-gigabyte overage rate is published.

You can cancel at any time and the plan runs to the end of the paid period, then the organisation drops to Free. There are no refunds for unused time. For comparison, Scalar’s Pro plan is $150 a month with one SDK included and $150 for each additional one, so four languages there cost $600 at up to 100 endpoints. Fern and Stainless both have free tiers but quote their larger SDK plans differently.

Who is Octri Best For?

Use Octri if you run a small API with a clean OpenAPI spec and want docs, several SDKs and an MCP server from one subscription under $100 a month. It also suits open source projects: a grant programme lifts the limits to ten languages and 1,000 endpoints in exchange for attribution.

Skip Octri if procurement needs SOC 2, a contractual SLA or a vendor with a track record. Skip the monitoring piece for now if you cannot explain to your own customers what the SDK they install reports and when. And if you only need docs, a docs-only platform will be simpler.

Best Octri Alternatives

Scalar

Scalar covers docs, SDKs and hosted MCP servers. Its Free plan is $0 with one SDK up to 25 endpoints. Pro is $150 a month, or $125 billed yearly, with one SDK up to 100 endpoints and 5 editor seats. Business is $600 a month. Additional SDKs are $150 to $600 a month each.

Stainless

Stainless is the established name in generated SDKs and now also builds docs sites and MCP servers. Its pricing page lists a $0 Free plan with up to 5 generators and APIs of up to 25 endpoints, then Starter, Pro and Enterprise tiers. We could not read the paid prices from the page, so check them directly.

Fern

Fern, now part of Postman, offers a $0 SDK plan with Python and TypeScript clients for up to 200 endpoints and automated publishing. The full ten-language set is on a custom Enterprise plan priced per SDK and billed annually. Its docs product has a separate free plan with 10 team members and 250 AI credits a month.

Final Verdict: Is Octri Worth It?

Octri is good value and more honest than most launches. Ten languages, docs, an MCP server and monitoring for $249 a month undercuts Scalar’s list prices by a wide margin, the Free plan is usable, and the legal pages say what is collected, where it is stored and what the company lacks. The packages we unpacked do what the vendor says.

It is also a month-old company asking to sit inside the SDK your customers install. Try the free spec audit and the Free plan, and generate one language. Hold off on switching monitoring on for third-party users until the guides and the Addendum say the same thing about who opts in. For a small team with a clean spec, it earns a 7 out of 10.