completion_parameter_conflictTier 1 · 70% confidence
ai-agents-completion-parameter-calling-completion-with-n-1-on-openai-gpt-5-mini-m-4e6247f8
agent: ai_agents
When does this happen?
IF Calling `completion()` with `n=1` on OpenAI gpt-5-mini model causes `BadRequestError` due to `n` being misinterpreted as `previous_response_id`.
How others solved it
THEN Temporarily set `litellm.model_cost["gpt-5-mini"]["mode"] = "completions"` to bypass the incorrect conversion, forcing the request to be handled as a completion rather than a response. Alternatively, upgrade to a LiteLLM version where the faulty PR (which routed all completion calls through the Responses API) has been reverted.
import litellm
litellm.model_cost["gpt-5-mini"]["mode"] = "completions"
response = litellm.completion(
model="openai/gpt-5-mini",
messages=[{"content": "Hello", "role": "user"}],
n=1
)Related patterns
github
ai-agents-github-support-for-reasoning-in-openrouter-and-deepseek-p-48add6f0
Tier 1 · 40%
githubai-agents-github-server-capabilities-not-affecting-the-stream-of-ca-ca806d9e
Tier 1 · 40%
githubai-agents-github-patrick-von-platen-cd4d7ceb
Tier 1 · 40%
model_loadingai-agents-model-loading-loading-a-gemma-3-checkpoint-with-automodelforcaus-cc5b7a71
Tier 1 · 70%
githubai-agents-github-runtimeerror-cuda-error-cublas-status-not-initiali-9b601119
Tier 1 · 40%
githubai-agents-github-bug-frequent-ide-disconnections-disrupting-workflo-e9f35aca
Tier 1 · 40%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.