Parameter Compatibility

Most standard chat parameters behave consistently in RouteAPI-compatible requests. Optional capabilities may vary by model, so confirm them in the console before production use.

Parameters to confirm

Parameter	What to confirm
tools	The selected model supports tool calls.
tool_choice	The requested tool selection mode is supported.
response_format	The model supports JSON mode or JSON Schema output.
stream_options	Streaming responses can return usage information.
reasoning	The selected model supports reasoning control parameters.
temperature	An explicit 0 value is preserved.
parallel_tool_calls	An explicit false value is preserved.

Explicit 0 and false

If the client sends:

{
  "temperature": 0,
  "stream": false,
  "parallel_tool_calls": false
}

RouteAPI treats these values as explicitly set and does not remove them just because they are 0 or false.

Best practices

• Confirm required capability support in the console before launch.
• Keep request parameters consistent between testing and production.
• When a model does not support a capability, prefer returning a clear client error.
• After changing parameters, compare request behavior through usage logs.