induwara.lk
induwara.lkDevelopers · AI APIs

AI Model Parameter Support Checker

Will this OpenAI, Claude or Gemini model accept the parameter you are sending? Get the verdict, the valid range and default, and the exact field name — so you can stop reading three sets of API docs to fix one 400 error.

By Induwara AshinsanaUpdated Jul 11, 2026
Check parameter support
Supported

temperature on GPT-4o

Field name
temperature
Valid range
02
Default
1

Porting check

GPT-4o
  • temperatureBreaksNot accepted by o3 — use reasoning_effort instead.
  • top_pBreaksNot accepted by o3; remove it from the request.
  • top_kUnsupported on both models.
  • presence_penaltyBreaksNot accepted by o3; remove it from the request.
  • frequency_penaltyBreaksNot accepted by o3; remove it from the request.
  • logprobsBreaksNot accepted by o3; remove it from the request.
  • logit_biasBreaksNot accepted by o3; remove it from the request.
  • stop / stop_sequencesNo changeSame field, same range — no change needed.
  • max tokens fieldRenameRename max_tokens → max_completion_tokens.
  • tools / function callingNo changeSame field, same range — no change needed.
  • structured / JSON outputNo changeSame field, same range — no change needed.
  • vision (image input)No changeSame field, same range — no change needed.
  • streamingNo changeSame field, same range — no change needed.
  • system promptRenameRename messages[role: system] → messages[role: developer].

Full support matrix

supportedrenamednot supported — click any cell to load it above.

Support matrix: models down the left, request parameters across the top. Check means supported, arrows mean the field is renamed, cross means not supported.
Modeltemperaturetop_ptop_kpresence_penaltyfrequency_penaltylogprobslogit_biasstop / stop_sequencesmax tokens fieldtools / function callingstructured / JSON outputvision (image input)streamingsystem prompt
GPT-4o
GPT-4.1
GPT-4o mini
o1reasoning
o3reasoning
o3-minireasoning
o4-minireasoning
GPT-5 (reasoning)reasoning
Claude Opus 4
Claude Sonnet 4
Claude Haiku 3.5
Gemini 2.5 Pro
Gemini 2.5 Flash
Gemini 2.0 Flash

Capability data is a static, versioned table compiled from the official OpenAI, Anthropic and Google API references. No request is sent to any provider. Sources and last-verified date are listed below the tool.

How it works

Every hosted LLM API accepts a slightly different set of request parameters, and the mismatches are silent until a request 400s. This tool encodes, for each model, whether a given parameter is supported, supported under a different field name, or not supported — plus its valid range, default value, whether it is required, and the recommended alternative when it is rejected. It is a lookup, not a calculation: nothing is sent to any provider, and the same input always returns the same answer.

The data comes straight from the official API references. Three rules do most of the work:

  • OpenAI reasoning models (o1, o3, o3-mini, o4-mini, GPT-5 reasoning) reject the sampling parameters entirely — temperature, top_p, presence_penalty, frequency_penalty, logprobs, logit_bias — and require max_completion_tokens in place of max_tokens.
  • Anthropic Claude caps temperature at 1.0 (not 2.0), requires max_tokens on every call, renames stop to stop_sequences, makes system a top-level string, and offers no penalty or log-probability fields.
  • Google Gemini keeps the same concepts but nests them under generationConfig in camelCase: topP, topK, maxOutputTokens, stopSequences, and responseSchema for structured output.

The porting check compares any two models across all 14 parameters and flags exactly what changes — what breaks, what needs renaming, where a range shrinks, and what becomes required — because that comparison is the real cause of most porting failures. The support matrix renders every one of the 196 model-by-parameter cells at once, so the answer is on-screen before you touch a control. A built-in cross-check confirms all 196 cells resolve against the source table on every build.

Worked examples

OpenAI o3

temperature

Not supported
  1. o3 is a reasoning model → sampling parameters are fixed.
  2. Sending temperature: 0.2 returns HTTP 400 unsupported_value.
  3. Fix: omit temperature; use reasoning_effort (low/medium/high).
  4. Also swap max_tokens → max_completion_tokens, or the call still 400s.

Claude Sonnet 4

frequency_penalty

Not supported
  1. Anthropic's Messages API has no penalty fields at all.
  2. frequency_penalty and presence_penalty are silently dropped or rejected.
  3. Fix: reduce repetition with temperature, top_p or top_k, or a prompt rule.
  4. Watch out: on the same model, temperature max is 1.0 — not 2.0.

GPT-4o

temperature

Supported
  1. GPT-4o is a standard chat model → full sampling support.
  2. Field name: temperature. Valid range: 0 – 2. Default: 1.
  3. top_p, penalties, logprobs and logit_bias are all accepted too.
  4. Porting the same call to Claude? temperature > 1 will then 400.

Frequently asked questions

Sources & references

The support table was last cross-checked against these official references on 2026-07-11. It is reviewed whenever a provider ships a new model family or changes a parameter's behaviour. This tool covers capability only — it does not recommend parameter values, decode error codes, or estimate cost; see the related tools below for those.

Related tools

Rate this tool
Be the first to rate

Comments & feedback

Spotted a bug or want an improvement? Tell us — our team reviews every comment, and good ideas get built. Comments are public and anonymous.

Found a parameter that behaves differently, or want a model added?

Email me at [email protected] — I re-verify against the docs and update within a day.