What's GPT-5 support status currently?

[grpaiva]

TL;DR:
Tried migrating from gpt-4.1 to gpt-5 in my project ("the simple way" - without lots of research) and some requests work. However, I'm still seeing errors on structured outputs (missing required fields in the model's response) and tool calling (specifically an HTTP 400 error about duplicate item IDs). Couldn't find clear migration guidance, am I missing something?

---

Hey guys!

I'm using the latest version: v0.86.0.

I tried switching from gpt-4.1 to gpt-5 in my project but encountered some weird errors. I checked here and in the docs for any required migration steps, but didn’t find anything consistent. While reading OpenAI’s documentation, I noticed there are new parameters such as:

"reasoning": {
  "effort": "minimal"
}

and

"text": {
  "verbosity": "low"
}

I've added those to some text generations like:

$response = Prism::text()
            ->using(Provider::OpenAI, 'gpt-5-mini')
            ->withProviderOptions(['text' => ['verbosity' => 'low'], 'reasoning' => ['effort' => 'minimal']])
            ->withSystemPrompt($prompt)
            ->withPrompt('Write a fortune cookie for the user.')
            ->asText();

This approach works for simple requests, but for more complex ones I’m still running into issues—specifically, missing required fields in structured output requests and the following errors when using tool calling:

error: Sending to model (gpt-5-mini) failed: HTTP request returned status code 400: { "error": { "message": "Duplicate item found with id rs_68ab99c342588195aec2898e8abcb9fe0ac6252a1b090d1b. Remove (truncated...)

and

[previous exception] [object] (JsonException(code: 3): Control character error, possibly incorrectly encoded at /Users/grpaiva/Documents/projects/skilldeck/vendor/prism-php/prism/src/ValueObjects/ToolCall.php:35)
[stacktrace]

Is GPT-5 fully supported already? Are there additional steps required before migrating?

[DanielSpravtsev]

TL;DR: Tried migrating from gpt-4.1 to gpt-5 in my project ("the simple way" - without lots of research) and some requests work. However, I'm still seeing errors on structured outputs (missing required fields in the model's response) and tool calling (specifically an HTTP 400 error about duplicate item IDs). Couldn't find clear migration guidance, am I missing something?

Hey guys!

I'm using the latest version: v0.86.0.

I tried switching from gpt-4.1 to gpt-5 in my project but encountered some weird errors. I checked here and in the docs for any required migration steps, but didn’t find anything consistent. While reading OpenAI’s documentation, I noticed there are new parameters such as:

"reasoning": {
  "effort": "minimal"
}

and

"text": {
  "verbosity": "low"
}

I've added those to some text generations like:

$response = Prism::text()
            ->using(Provider::OpenAI, 'gpt-5-mini')
            ->withProviderOptions(['text' => ['verbosity' => 'low'], 'reasoning' => ['effort' => 'minimal']])
            ->withSystemPrompt($prompt)
            ->withPrompt('Write a fortune cookie for the user.')
            ->asText();

This approach works for simple requests, but for more complex ones I’m still running into issues—specifically, missing required fields in structured output requests and the following errors when using tool calling:

error: Sending to model (gpt-5-mini) failed: HTTP request returned status code 400: { "error": { "message": "Duplicate item found with id rs_68ab99c342588195aec2898e8abcb9fe0ac6252a1b090d1b. Remove (truncated...)

and

[previous exception] [object] (JsonException(code: 3): Control character error, possibly incorrectly encoded at /Users/grpaiva/Documents/projects/skilldeck/vendor/prism-php/prism/src/ValueObjects/ToolCall.php:35)
[stacktrace]

Is GPT-5 fully supported already? Are there additional steps required before migrating?

I tested, you sending wrong parameters
Reasoning should be: 'reasoning' => ['effort' => 'low'],

You can find other options here based on the model you want to use
https://docs.aimlapi.com/api-references/text-models-llm/openai/gpt-5-mini#post-v1-responses

[mnwalker]

'temperature' is not supported with this model.
Getting this with gpt-5 which feels like something Prism should be able to auto detect and just not use this option for any models that dont support it.