Are SDKs and SDK generation common these days?
New dev.. trying to assess whether or not with the explosion of AI and MCP more recently, if developers even bother with SDKs any more or just use AI to code things and not care about SDKs.. in particular those that mask the APIs they make use of?
For that matter, API product/producers.. do they have any need to build SDKs any more? Not too long ago while in college I was learning about APIs, and we built things like simple http clients that called APIs, as well as used a tool called Postman.
But recently I am delving a bit in to the AI world, and I am wondering how company's like Stainless, SpeakEasy, APIMatic and Fern.. and I guess Kiota (from what I dug up) are able to stay in business if at least to me it appears developers can now just have AI build the code in their GUI or CLI or API consuming apps to do the API Calls directly. What benefit would there be in a) using an SDK dependency in my client/consumer code and b) for API providers.. be it Stripe, Amazon or small startups, to provide SDKs for their APIs?
Should I bypass SDKs in general and just use AI to build my own custom http client since it literally takes like a minute or two for AI to do that? Have it read the API docs (since that too seems to be very possible with AI using MCP like context7) and just OWN the code rather than depend on 3rd party SDKs.. even if the company of the API provides them? Or is there a reason to utilize these SDKs?
My product idea would integrate with OTHER vendors (APIs) and I would provide an API as well, should I even bother generating SDKs in different languages for consumers of my API to use?
Posted Nov 5, 2025, 1:45 AM UTC