Octri.dev
Product Hunt fmerian
Octri.dev turns an OpenAPI spec into docs, SDKs, and an MCP server. It also feeds SDK errors back to you, so broken integrations show up early.
Based on reporting by Product Hunt, fmerian — read the original for the full story.
Summary, retelling and take written by AI under human oversight; images are AI-generated illustrations. How we work · Report an error
Octri.dev is launching with a simple pitch: upload an OpenAPI spec and get a documentation site, client SDKs, and an MCP server back out the other side. The company says the SDKs cover ten languages: TypeScript, Python, Go, Rust, Ruby, PHP, Java, Kotlin, Swift, and Dart.
The sharper bit is the feedback loop. Octri says each SDK reports its own production errors, which means teams can spot integration failures before those problems turn into support tickets. That is a pretty practical idea, and a lot less flashy than the usual API tooling buzzwords.
It also plugs into GitHub sync, so every merge regenerates the docs and generated code. That matters because generated API assets tend to drift fast once real development starts. Keeping docs and SDKs tied to the spec on every merge is the kind of boring automation that saves a lot of cleanup later.
The product is aimed at teams that want their API surface to ship as a package: docs for humans, SDKs for developers, and an MCP server for AI agents. Octri is positioning itself as the thing that keeps all three aligned without making someone babysit the whole stack.
My take — AI-written commentary, not fact-checked reporting
This is the kind of infrastructure product that wins by being annoying in the right way: it removes one more excuse for shipping half-broken API tooling. The real story isn’t the ten languages, it’s the reporting loop back from the SDKs — that’s where the pain lives. Most teams do not need more swagger; they need fewer surprise tickets.
Read more about this at: Product Hunt