![]()
The reasons I am highlighting these only a few days after launch:
- Should have been fixed/updated prior to launch (imagine someone wanting to switch over from the twitter bot to openai; it would be that much more annoying without proper docs)
- Every time I come back to the openai docs, they are not fixed for months to match new models, only adding to time spent on deconfusing the code
- these are the major parameter changes which make prior functions incompatible with new models
- Reasoning effort on Responses API:
-
o-series models only ← incorrect, also includes GPT-5 family and likely all the new models
Configuration options for reasoning models.
Constrains effort on reasoning for reasoning models. Currently supported values are
minimal,low,medium, andhigh← incorrect, o3 and o4 family will give error when using “minimal”
- Verbosity on Responses API
- Currently supported values are
low,medium, andhigh. ← wrong; none of the models support this, except for GPT-5 family models; o3, o4, etc only support “medium” - Verbosity being listed as it is now in the docs suggests it is its own parameter. It is a subparameter of text. This can also be seen in the sample Response object they provide on the left side; no it cannot, because verbosity does not exist there.
-
verbosity = "low" # gives error -
text = {"verbosity": "low"} # works
-
- Temperature
- NOT supported in the o3, o4 or new family of GPT models; it will give error unless ignored or set to 1
-
All of the above 1-3, but for the Chat Completions API documentation
-
stop parameter in Chat Completions API
- does not work for GPT 5 family (and does not even work in the Responses API at all)



