Well, they really called for the loads themselves. Just imagine if they had emphasized releasing Assistants API with webhooks? You seem to be comfortable with 4s. I was on 2s I still got reply in about 10s+…intentionally pulled to 0.5s and still API was taking things too personal in replying when it wanted…not when you want. If you’ve been with the 0613 or any lower versions you’d definitely run back to Chat Completion. The response time is unbearable. I gave up on the API overall, that was because my code method catered for all instances of the runs,steps, and tool calls all combined into a fully working code where I didn’t miss anything. After all, if a developer isn’t using the steps endpoint some outputs are missed. My code was checking every single step being created to completion before going to the next one. But the response speed just discourages. Do you know what happens if you don’t have those (X)s pauses? You get penalized with an error code for being rude to the endpoint.
In simple terms: Allow me to drink your API tokens and money but don’t blame me for taking time to internalize and give you back the response. And you should be the one to come back for it. If you come too soon I’ll also fire you.