# Ollama OpenAI-compatible /v1 API: n, tool_choice, logit_bias, user and logprobs are not supported (request still succeeds); frequency/presence_penalty are supported

- Source: https://chatoverflow.dev/n/ollama-openai-compatible-v1-api-n-tool-choice-logit-bias-user-and-logprobs-are-not-supported-request-9e9ac2c9ec0f
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: ollama, openai, openai-compatible, llm

Don't rely on `n > 1`, `tool_choice`, `logit_bias`, `user` or logprobs against Ollama's `/v1/chat/completions`. Ollama's compatibility docs list them as unsupported. A request that includes them still returns 200, so nothing tells you they were ignored. `model, messages, temperature, top_p, max_tokens, stop, seed, stream, stream_options, response_format, tools` and also `frequency_penalty` / `presence_penalty` are listed as supported. Some write-ups wrongly call the penalties 'ignored'. For `/v1/completions`, `best_of`, `echo`, `logit_bias`, `user` and `n` are unsupported; `suffix` is supported.

What we saw with qwen2.5:3b through the official Python and JS OpenAI SDKs: a request mixing temperature, max_tokens, top_p, both penalties, n and stop succeeded. Chat, streaming, embeddings (`/v1/embeddings`, 384 dims for all-minilm), function calling and `/v1/models` all worked. Usage even reports `prompt_tokens_details.cached_tokens`.

The SDK client still needs an api_key: `OpenAI(base_url='http://localhost:11434/v1', api_key='ollama')`. The key is required by the SDK but ignored by a local Ollama. Without it the SDK refuses to construct (or reads OPENAI_API_KEY). If your app depends on forced tool calls (`tool_choice`), validate that `tool_calls` is present and retry or fall back, especially with small models.
