4 ms·
This is their first model to only be available via the new Responses API - if you have code that uses Chat Completions you'll need to upgrade to Responses in or
by simonw 2y ago
This is their first model to only be available via the new Responses API - if you have code that uses Chat Completions you'll need to upgrade to Responses in order to support this.
Could take me a while to add support for it to my LLM tool: https://github.com/simonw/llm/issues/839 https://github.com/simonw/llm/issues/839
- icelancer 2y agoOh interesting. I thought they were going to have forward compatibility with Completions. Apparently not.
- dtagames 2y agoIt does. There are two endpoints. Eventually, all new models will only be in the new endpoint. The data interfaces are compatible.
- deleted 2y ago[deleted]
- dtagames 2y agoIt shouldn't be too bad. The responses API accepts the same basic interface as the chat completion one.
- Tiberium 2y agoEven the basic interface is different, actually - "input" vs "messages", no "max_completion_tokens" nor "max_tokens". That said, changing those things is quite easy.
- simonw 2y agoThe harder bit is the streaming response format - that's changed a bunch, and my tool supports both streaming and non-streaming for both Python sync and async IO - so there are four different cases I need to consider.
- dtagames 2y agoIf it's easier, just ask Cursor to make the upgrade. Give it a link to the OpenAI doc. You might be surprised at how easy it is.
- luke-stanley 2y agoSimon, I see if via Chat Completions as well as Responses in their API platform playground.
- simonw 2y agoI just tried sending an o1-pro prompt to the chat completions API in the playground and got: This is not a chat model and thus not supported in the v1/chat/completions endpoint. Did you mean to use v1/completions?
- luke-stanley 2y agoSorry, since the Platform UI featured it as an option, I figured OpenAI might enable o1-Pro via the chat completions endpoint, I just got around to testing it, and I also get the same 404 `invalid_request_error` error via the platform UI and API. It's such an odd and old 404 message, to suggest using the old completions API! It's hard to believe it could be an intentional design decision. Maybe they see it as an important feature to avoid wasting (and refunding) o1-pro credit. I noticed that their platform's dashboard queries https://api.openai.com/dashboard/which https://api.openai.com/dashboard/which lists a supported_methods property of models. I can't see anything similar in the huge https://raw.githubusercontent.com/openai/openai-openapi/refs/heads/master/openapi.yaml https://raw.githubusercontent.com/openai/openai-openapi/refs... schema yet (commit ec54f88 right now), and it lacks mention of o1-pro at all. Like the whole developer messages thing, the UX of the API seems like such an after-thought.