Are certain OR parameters deprecated?

[vale hearth]

@pastel kiln

Description:
api/v1/responses and SDK Call Model supported the following: topP, topK, frequencyPenalty, presencePenalty

Where are the rest of the parameters?
repetition_penalty, min_p, top_a, seed, stop

They are only acknowledged in https://openrouter.ai/docs/api/reference/parameters
(I remember each model used to show what parameters it accept, and the "default" values)

Does anyone know what happened to the other parameters?
Are the parameters missing form doc silently accepted? or are they deprecated and silently discarded?

Regardless popular tools like sillytavern still seems to show them as options...

Thanks

I'm an AI assistant - my answers may be incorrect and I cannot see screenshots. Please verify information with the OpenRouter docs.

To answer your question about parameter support and deprecation:

• Each model on OpenRouter advertises a list of supported parameters in its documentation page (for example, see the "Supported Parameters" section for Gemma 3 27B). Not all models support all parameters, and the accepted parameters may differ between models.
• "Parameters not listed in a model's 'Supported Parameters' section are typically not supported for that model—either ignored or rejected." The API docs reference all possible parameters, but model-specific support is determined by the model documentation.

To address your specific concerns:

• The parameters you mentioned (such as repetition_penalty, min_p, top_a, seed, stop) are still present in the API Parameters Reference, but you must check a model's documentation page to confirm support and defaults.
• If a parameter is not shown under a model's "Supported Parameters," it is usually not supported for that model. There's no explicit "deprecation" notice; unsupported parameters are typically ignored or may cause an error depending on the backend.
• Model documentation pages no longer always show "default" values for parameters—this information may have been removed or is only present in select cases.

Quoted from the Gemma 3 27B model page:

"Supported Parameters: Max Tokens, Temperature, Top P, Stop, Frequency Penalty, Presence Penalty, Seed, Top K, Repetition Penalty, Response Format, Tools, Tool Choice, Structured Outputs"

Fo...

...r authoritative info on parameter support:

• Always refer to the "Supported Parameters" section on the individual model page
• The Parameters Reference lists all possible parameters, not necessarily supported by every model

If you believe a parameter should be supported but isn't working, please provide:

1. The exact model identifier you are using
2. The full API call (with parameters)
3. Any error or response you receive

This will help mods and support debug further.

References:

• "Supported Parameters" sections — Gemma 3 27B, Llama 3.2 3B Instruct
• API Parameters Reference

Let me know the model, code, and error if you want a deeper check!

-# This is an automated response powered by Answer HQ. Use !mute to stop the bot from responding, or !close when your question is resolved.

[pastel kiln]

Hi thanks for the links
It seems like i cannot find the following text "Supported Parameters" in the given page https://openrouter.ai/google/gemma-3-27b-it
Your information on the page might been outdated, or i am receiving a different version, i did recall "Supported Parameters" used to be mentioned on a model page, but i cannot find it now

regarding https://openrouter.ai/docs/api/reference/parameters
it is true that these parameters are mentioned there, they describe what existed
but the structure of "where to put them while making a request" is never clearly conveyed

the endpoint docs for either endpoints https://openrouter.ai/api/v1/chat/completions and https://openrouter.ai/api/v1/responses did not describe the appropriate location as an conditional option that may be applicable depending on selected model

and while using the official SDK there's no way to inject these extra parameters, typescript will not accept these extras
https://github.com/OpenRouterTeam/typescript-sdk/blob/main/src/models/openresponsesrequest.ts#L290
https://openrouter.ai/docs/sdks/typescript/api-reference/models/openresponsesrequest

[vale hearth]

You're correct—recent model pages like https://openrouter.ai/google/gemma-3-27b-it no longer display a "Supported Parameters" section. Previous documentation did show this, but as of now, that info is missing from the visible model pages. You are not missing anything; the docs and UI have changed.

Regarding the location and injection of parameters:

• The API Parameters Reference lists all possible parameters, but does not specify for each model which are supported or where exactly to place them in the request.
• For API requests, all sampling and control parameters (like repetition_penalty, top_p, top_k, min_p, etc.) are typically sent in the top-level JSON body of your POST request to /api/v1/chat/completions or /api/v1/responses. There is no conditional structure for these parameters—they are always top-level fields.
• There is no current documentation that clearly maps parameter support per model, or specifies "conditionally allowed" fields by model in request examples. The docs only mention: "See the Parameters reference for descriptions of each parameter, and refer to the model page for supported parameters." API Reference Overview.

Regarding SDK limitations:

• The TypeScript SDK model currently uses a strict request type that only allows specific fields. This means you cannot send arbitrary or undocumented parameters using the SDK if they are not explicitly defined in the type. This is a TypeScript safety feature, but it limits your ability to experiment with unlisted parameters.
• The [TypeScript SDK API Reference](<htt...

...ps://openrouter.ai/docs/sdks/typescript/api-reference/models/openresponsesrequest>) confirms that only the documented fields are accepted. Unsupported or deprecated parameters are rejected at compile time or ignored at runtime.

Summary:

• Model pages no longer list supported parameters.
• All parameters should go in the top-level body of the request.
• The TypeScript SDK does not allow custom parameters not present in its type definitions.
• There is no clear, up-to-date mapping of which parameters are silently accepted or ignored per model.

If you need to use extra parameters not supported by the SDK, you may need to switch to direct HTTP requests and manually construct your payload, bypassing the SDK type checks.

"I don't have specific documentation for these SDK and parameter issues. Please verify with the mods or check the OpenRouter docs directly for the most accurate information."

-# This is an automated response powered by Answer HQ. Use !mute to stop the bot from responding, or !close when your question is resolved.

[wicked spear]

@pastel kiln Probably bad UI design especially for mobile users, but if you mouseover the provider info, an arrow shows up to expand it. I could've sworn the arrow was always visible before.

Though I notice the original question was about v1/responses API which clearly don't list some in the docs.
Edit: actually v1/chat docs doesn't (anymore?) list min_p either

[pastel kiln]

Oh thank you very much, i swore it was surfaced before, but i couldnt find it
looks like it been moved under the provider's detail instead(make sense, just not what i was expecting to be hidden)