Skip to main content
A preset is a saved, versioned configuration — model or model chain, routing policy, system prompt, and sampling parameters — addressed by a slug. Your application sends only the messages; the preset supplies everything else. That means you can change the model, tighten a routing policy, or edit a system prompt without shipping a code change.

​
Call a preset

The request body is the ordinary Chat Completions body with one difference: messages is the only required field. The preset’s saved model, routing, system prompt, and parameters are applied for you. The response is a standard chat completion, plus headers identifying which preset and version served the request: Log the version header — it tells you which configuration produced a given response after the preset has moved on.

​
Overriding per call

Pass model or models to override the preset’s chain for a single request; every other Chat Completions parameter (temperature, max_completion_tokens, stream, stop, seed, and the rest) is accepted and takes precedence over the saved value.
Streaming, tool calling, and fallback chains behave exactly as they do on /chat/completions.

​
Managing presets

Create and version presets in the developer console. Publishing a new version changes what the slug serves on the next request — no redeploy on your side.