Chat model parameters

The inspected chat contract requires model and messages. Optional parameters are gateway request controls, not proof that every model supports every advanced feature.

Request bounds

The gateway validates max_tokens from 1 to 131072, n from 1 to 8, temperature from 0 to 2 and top_p from 0 to 1. Its default max_tokens is 4096. These validation ceilings are not model context-window guarantees.

Advanced options

tools, tool_choice and response_format are optional fields. Route and model support must be verified separately. See chat reference, tool calling and structured outputs.

Unsupported parameters

A compatibility layer does not establish universal provider-specific parameter support. Start with the smallest valid request, check the reference, and treat 400 as a request correction rather than a retry trigger.

Verification and next steps

These instructions describe inspected repository contracts and safe integration boundaries. They do not prove live account access or external provider behavior. Continue with developer answers, API overview and verification limits.