Going further into it: the expected user experience for your team is that you create a PR in your own API repo, a GitHub action triggers builds for everything and gives you a summary via PR comments where you can directly see diagnostic feedback, see the exact diff for each SDKs, provide the commit message for your end users. Once your PR is merged we push changes to all your SDK/docs repos and prepare a release PR ready for your team to review and merge. You merge it, everything gets released to your end users.
Now what we build goes way further than that: we have a web platform where you can live edit your Stainless config file and preview your SDKs, a fairly complex diagnostic system, a really cool system that allows you to add your own custom code on top of any generated SDK directly via git — the whole repo is something you can modify to your wishes, we keep track of your custom changes and always reapply on top of the latest codegen output. And a lot of other features (I’m biased because I designed and implemented the public version but I personally really like our spec transforms, they let you apply changes to your spec file downstream, just by modifying your stainless config file).
Does that make sense?
Alex vision has always been to generate code other engineers would love reading. It’s something I know the team is very proud of and what attracted most of us. We all joined because we wanted to raise the quality of developer experience across the board and I believe that we did it successfully
We might have our opinions on AI and slop, but in the end of the day this was a business play and it worked out for the players. Separate that from the actual product and u can respect they did really well for themselves.
See https://www.stainless.com/customers/ for an overview
edit: they sure do
I don’t understand your point, things look fairly clear to me, assuming you’re familiar with that part of the industry. We didn’t hide behind buzzwords and show you the end product right away
--- start quote ---
Best-in-class interfaces for developers and agents
Great agent experience is built on great developer experience. Stainless helps you deliver both, with robust and idiomatic SDKs, documentation that keeps up with your API, and state-of-the-art MCP servers, all derived from your OpenAPI spec.
--- end quote ---
There would be no questions asked if you had the SDK's copy on your front page. Or whatever you wrote here: https://news.ycombinator.com/item?id=48191376
They might be a big part of the reason why claude code can edit notion docs for you pretty easily
