Octri
My siblings and I are building Octri, an all-in-one platform for API teams. https://octri.dev You give it an OpenAPI, Postman, or AsyncAPI spec, and it generates and manages: - Editable API docs with an API playground, RAG-based chat, custom components, and other interactive features. - Idiomatic SDKs in 10 languages. We’ve been building these alongside developers experienced in each language rather than relying on a single generic codegen template. The part we’ve spent a lot of time on is customization. There’s a visual editor with a real-time code preview where you can change things like: - client initialization patterns - positional args vs DTOs vs kwargs - HTTP client/library - tree-shakability - method structure and naming - and quite a bit more The goal is for generated SDKs to feel like something you would have written by hand rather than obviously generated code. - API + SDK monitoring that maps telemetry back to your API spec. It can identify slow SDK methods and API paths, track uptime/status announcements, capture errors and stack traces, etc. We’ve also built PII filtering into the telemetry pipeline with GDPR considerations in mind. - Spec Audit, which we’re planning to open source. It scores an OpenAPI spec, explains problems it finds, and can automatically fix a number of them. A big reason we started working on this is that API tooling in this space often feels optimized for enterprise buyers rather than the developers actually using it. We also kept running into rough UX around editing docs, customizing generated SDKs, and specs failing on first import because of small incompatibilities. We want Octri to have a much lower barrier to entry: affordable enough for smaller teams, highly customizable, and able to improve/fix inputs rather than just failing when a spec isn’t perfect. We’re still in beta and looking for a few design partners who have real APIs/SDKs they’d be willing to run through it. In return, we’d offer favorable long-term pricing for early adopters. I’d also genuinely appreciate feedback from people here who maintain public APIs or SDKs: what part of your API tooling workflow is currently the most painful?