Product or project idea? Is anyone making API integrations easier, like what OpenAI is doing with their docs -> plugins tech? Not "are you a making a plug-in", more "are you making it easy for other devs to add integrations to their own projects?" I need to integrate some old and horrible but well documented API's (that I don't control) into a system I'm building. I don't want to do this as a ChatGPT plugin because I don't every API call to incur token costs and multi-second waits. I want to feed the API docs into something once and get back a purpose-built SDK in the language of my choosing that does exactly what I need it to do. Anyone built that or building it? Am I dreaming in thinking someone could build this?

Like this? https://writings.stephenwolfram.com/2023/04/instant-plugins-for-chatgpt-introducing-the-wolfram-chatgpt-plugin-kit/

The Wolfram thing is very cool but I think it's just making it easier to integrate 3rd party API's with ChatGPT. Every time you call the 3rd party API using the Wolfram approach you're actually sending your request behind the scenes to OpenAI's servers and getting the result back by way of OpenAI's servers (with lots of ML-related costs incurred for having OpenAI proxy those requests for you). That makes sense if you're building a ChatGPT app but it's not a great approach if you're running more conventional server code that just needs to hit a 3rd party API for some reason. I'm hoping someone is making something that can read API docs (the way OpenAI and Wolfram are) to generate a custom SDK in whatever language you want (JavaScript/TypeScript/Java/Go/C# etc.) that can be added to a repo to help a server hit that API directly without needing to go through GPT to hit the API. Edit Added: If I'm wrong about the way the Wolfram thing is working behind the scenes, please let me know!

@Don Alvarez makes sense, although if you do build it as a chat, GPT, plug-in, chat, GPT could edit the SDK as it needs maintenance. Something to think about.

@Jazear Brooks true, but I think one could just run the SDK constructor as part of the build process and get the same benefit at much lower financial and latency cost (plus 3rd party API's shouldn't change often - if they do there's a much more serious problem with that API than just needing an SDK)

@Don Alvarez I’m working on building this now!

I am really interested by this @Shahbaz Ahmad as i have build in a hackathon usng langchain openapi agent a way to go from text to request