Create an OpenAI-compatible chat completion
Headers
Bearer API key.
API key alternative for Anthropic-compatible clients. Authorization takes precedence when both headers are present.
Body
OpenAI-compatible chat completion request.
Public model ID.
1OpenAI-compatible chat messages.
1Abliteration safety categories to block for the latest user turn. Parent categories include their narrower child categories.
harassment, harassment/threatening, hate, hate/threatening, illicit, illicit/violent, self-harm, self-harm/intent, self-harm/instructions, sexual, sexual/minors, violence, violence/graphic Whether to stream the response.
1 <= x <= 9999901 <= x <= 9999900 <= x <= 20 <= x <= 1-2 <= x <= 2-2 <= x <= 21 <= x <= 128Legacy compatibility toggle. The gateway translates this into backend-owned model-profile reasoning controls.
OpenRouter-style reasoning controls translated by the selected model profile.
OpenAI/vLLM-compatible reasoning effort control.
none, minimal, low, medium, high, xhigh, max, ultracode Whether reasoning fields may be returned when the runtime emits them.
Accepted for OpenAI compatibility, but not used for V1 abuse correlation and not forwarded to model runtimes.
64Accepted for OpenAI compatibility but not forwarded to model runtimes.
512Client structured-output capability declaration accepted for compatibility. It is ignored and never forwarded; use response_format to request an output format.
none, auto, required none, auto - ChatCompletionResponseFormatText
- ChatCompletionResponseFormatJsonObject
- ChatCompletionResponseFormatJsonSchema
low, medium, high 512in_memory, 24h Response
Successful Response