Octri.dev - Generate customizable Docs, SDKs, MCP server, and monitoring
by•
Upload an OpenAPI spec and Octri generates a fully customizable documentation site, high-quality client SDKs in ten languages (TypeScript, Python, Go, Rust, Ruby, PHP, Java, Kotlin, Swift, Dart) and an MCP server so AI agents can call your API.
The new part: every SDK reports its own production errors back, so you see integration failures before your users file tickets. GitHub sync regenerates everything on every merge.
Replies
the "SDK reports its own production errors back" part is the one I'd actually pay for, docs and SDK generation are table stakes at this point but almost nobody closes the loop on what happens after a user integrates. was literally in a forum thread earlier today about a team shipping a test that passed without ever causing the failure it claimed to catch, and this is the same problem from the other side - an SDK that looks fine in a demo but silently breaks for one specific language or edge case in prod. does the error reporting tell you which generated SDK (language/version) is failing, or just that an integration somewhere is throwing
@galdayan Hi Gal, Thanks a lot!
indeed the monitoring is going to be a great feature to keep teams in the loop and easily identify problems without the back and forth that they usually go through to just identify a small edge case bug!
The reporting is per language and gets deminified and points exactly where the failure is happening! We also auto group all errors to avoid the user being flooded by the same error.
Happy to answer any other questions you have regarding this feature as it's pretty new to the industry to be shipped in a client SDK.
@emad_khair per-language plus auto-grouping covers the two things I was actually worried about - a vague "something failed somewhere" is almost useless once you've got ten SDKs in the wild. auto-grouping makes me curious about one more thing: does it also catch the "same root cause, different symptom" case, like a Python SDK throwing a type error and a Go SDK throwing a nil pointer because the same upstream field went missing - or does grouping stay scoped to one language at a time
This is a really interesting idea! I love how you turn an API into something much easier to work with instead of making developers handle everything manually.
I’m currently building my own software products, and I can already see how something like Octri could save me a lot of time, especially around API documentation and SDK generation.
Really well thought out. Congrats on the launch!
@elghanam Thanks a lot Mohammed for your feedback and support! We are very glad to hear that developers are seeing the value that Octri provides! 🙌