> As we focus on Claude Platform capabilities and connecting agents to APIs, we’ll be winding down all hosted Stainless products, including our SDK generator. Starting today, new signups, projects, and SDKs will not be available.
> If you’re a Stainless customer, visit app.stainless.com/transition for help transitioning from Stainless-managed products to other options. As always, you own the SDKs you’ve generated to date, and have full rights to modify and extend them however you wish.
I know that common reasons for acquisitions are IP, talent, or reducing competition.
It seems like IP can't be the reason here. How is this strategically advantageous to Anthropic?
The amount of money thrown at it means at some point the words Return on Investment were going to appear.
It’s the classic loss leader applied to trillion dollar (across the market) capital investments.
Allowing users to take advantage of their monthly/weekly/daily token limits with the software of their choosing is a perfectly valid expectation.
Restricting it to their own underperforming, buggy TUI client is textbook walled garden.
I don't understand how investors continue to fund this nonsense. Anthropic wasting money on this should be an overwhelmingly strong signal that the AGI hyoe is blatant fraud and that software engineers are clearly not replaceable if they have to buy them for some tertiary, fifth-order concern so far removed from their main business. Yet they just keep getting more and more money dumped on them.
I hope they make it open source!
> Founded in 2022, Stainless has powered the generation of every official Anthropic SDK since the earliest days of our API.
edit: bah. no more HN before coffee.
This has to be somewhat anti-competitive. Why else sunset the SDK generator service but to hurt any other company (OpenAI, etc) who relies on these for their SDKs?
I don’t think so. They were available to anyone with the money and Anthropic acted first.
I doubt attempting to hurt OpenAI was the primary reason for the acquisition.
Maybe it’s different now; Bill Gates “wanting to cutoff Netscape’s air supply” and threatening to cancel the Windows license of PC manufacturers who shipped Netscape’s browser on their PCs… now that’s anticompetitive. They had 95% market share.
Bill was like “That's a nice PC business you have there; would be a shame if something were to happen to it.”
My preferred approach for doing this is to have a hand-rolled SDK generator that reads the request, response and error models out of the microservice project and emits the same in each language targeted by the SDK, along with a minimal stub that calls the API.
You then spend 15 minutes at most, customizing the stub if needed, if you need custom behaviours like streaming.
Been on my mind to explore that issue, because I run one of those API services that don't have an OpenAPI spec, but I have other priorities pulling my attention away from that idea. I just wish it was all handled.
For better or worse, it's an acquihire.
not anymore lol