diff --git a/docs/providers/openai-compatible.md b/docs/providers/openai-compatible.md index 2307884f..4d81e213 100644 --- a/docs/providers/openai-compatible.md +++ b/docs/providers/openai-compatible.md @@ -38,6 +38,7 @@ You'll find these settings in the Zoo Code settings panel (click the + +```json +{ + "metadata": { + "completion_window": "balanced" + } +} +``` + +Zoo Code validates the JSON before saving the provider profile and adds the fields to streaming, non-streaming, and single-completion requests. The top-level value must be an object. + +Extra Body cannot override fields managed by Zoo Code, including the model, messages, streaming mode, tools, reasoning settings, temperature, and token limits. Use the corresponding Zoo Code setting for those fields. Do not put API keys or other secrets in Extra Body because provider profiles can be exported. + +--- + ## Native Tool Calling Zoo Code uses **native tool calling** exclusively. This is the only supported tool protocol -- there is no XML-based fallback. diff --git a/static/img/openai-compatible/extra-body.png b/static/img/openai-compatible/extra-body.png new file mode 100644 index 00000000..bc306195 Binary files /dev/null and b/static/img/openai-compatible/extra-body.png differ