10 ms·
We handle over 1M requests per month using the Assistant API on https://rispose.com https://rispose.com which apparently will get depreciated mid 2026. Should w
by cosbgn 2y ago
We handle over 1M requests per month using the Assistant API on https://rispose.com https://rispose.com which apparently will get depreciated mid 2026. Should we move to the new API?
- jstummbillig 2y agoEventually, yes. The addressed Assistant API near the end of the the video: They say there will be a transition path, once they built all Assistant features into the new API, and ample time to take action.
- nknj 2y agothere's no rush to do this - in the coming weeks, we will add support for: - assistant-like and thread-like objects to the responses api - async responses - code interpreter in responses once we do this, we'll share a migration guide that allows you to move over without any loss of features or data. we'll also give you a full 12 months to do your migration. feel free to reach out at nikunj[at]openai.com if you have any questions about any of this, and thank you so much for building on the assistants api beta! I think you'll really like responses api too!
- marko-k 2y agoIf Responses is replacing Assistants, is there a quickstart template available—similar to the one you had for Assistants? https://github.com/openai/openai-assistants-quickstart https://github.com/openai/openai-assistants-quickstart