Octri.dev

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!

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

When an SDK sends back a failed call, what data goes with it? Can I make sure no request bodies or user info are included?

Amazing idea. Love it. Super excited to try it out on my own. Congrats on the launch though!

Hey @emad_khair Really like the idea of closing the loop between SDK generation and what actually breaks in production. How does Octri handle API changes over time, can it detect breaking changes in the OpenAPI spec and flag which generated SDKs or existing integrations might be impacted before a new version is shipped?

Huge congrats for launch, great to see a solid free tier alongside dedicated support for open-source projects.

This looks super useful ! Having the SDKs report their own failures back automatically is a massive time saver. Quick question : how hard is it to add custom CSS to the generated docs site ?

Python and TypeScript SDK generation usually breaks on edge cases excited to test this, congrats for shipping @Octri.dev team

I like that the SDKs are not just generated once and left alone. The production error feedback makes the whole workflow feel muh more practical for real API integrations.

congrats on getting this out the door.. will there be options to customize the doc themes in the future?

Hi Product Hunt, I'm Emad, one of the makers of Octri. 👋If you ship an API you know the routine: write the docs by hand, bolt on an SDK generator, then have no idea when those SDKs break inside someone's production app. Octri does the whole thing from one OpenAPI spec: a docs site, SDKs in ten languages (TypeScript, Python, Go, Rust, Ruby, PHP, Java, Kotlin, Swift, Dart) and an MCP server so Claude or Cursor can call your API.What is new though? Let me tell you! The SDKs monitor themselves. A failed call in a user's app comes back as a de-minified stack trace tagged to the exact release. No separate error-tracking setup! more about how it works and its security here: https://octri.dev/monitoringGitHub sync regenerates and republishes everything on every merge. Free tier is available to try it out and keep it if your API doesn't need more than the offered limits + we offer an OSS program as well for the open-source community! more about it here: https://octri.dev/open-sourcePoint it at your own spec and try it out free! All comments and feedback are welcome. We'll be here answering every one of them!