Lately, there have been incompatible changes being released to File Uploads and Responses api making it harder to uptake and build features while handling production issues. For applications that are in production for the last 12 months+ we have to provide SLAs to our customers and breaking changes to the apis without any doc updates or release notes causes customers to lose trust. I would like to see clear documentation, one forum where API updates are communicated. Model enhancements and releases should be decoupled from API releases and if the path to migrate from chatCompletions to ResponsesAPI is not clear especially on the ROI , companies will stay on the chatCompletions for longer and that needs to be maintained as an industry standard. ResponsesAPI & AgentSDK work really well for agentic use cases but not every startup and enterprise is ready to fully go all in on agents based on customer needs and market conditions, it’s still in its nascent stage. Finally to build native voice ai prototypes, the real time conversations api also needs to be hardened. I am hoping there is focus in the coming months on strengthening API Development and Production Support for usage of these APIs in enterprise applications. The differentiation for OpenAI has always been Model Intelligence and Developer Ease of Use - let’s get the developer ease of use as as a top priority.
2 Likes