Configure Chat Completions
What connection validation actually sends
All three model connection schemas accept exactlybase_url and model in config. The URL must use HTTPS without embedded username/password, query parameters or a fragment. The model ID is a nonempty string of at most 200 characters. Put credentials in the connection credential field, not in the URL or config.
Each validation request has a 30-second timeout and rejects redirects. It checks protocol shape, not that the answer literally equals OK. Responses may pass validation with an incomplete response, so ready is not proof of task completeness or sufficient output budget. No validation request exercises streaming, Tool calls or multi-turn conversation.
For an illustrative base
https://model.example/service/v1/, Chat Completions targets https://model.example/service/v1/chat/completions. A root ending in an operation such as /chat/completions is not automatically corrected. Configure the service’s supported API root; do not guess a path from the vendor name. This example domain is not a usable endpoint.
The creation snippets create a new connection every time. Persist the returned connection ID and use update/validate/enable for later changes. If creation’s response is lost, inspect existing records before rerunning the create snippet. A friendly display name is not a unique request key.
Complete a task with a recorded endpoint
For a concrete Chat Completions starting point, the November 18 matrix recordshttps://api.minimaxi.com/v1, model MiniMax-M3, and built-in Pi 1.5.2 / OpenCode 1.2.27 through independent Python and TypeScript tasks. Supply your own authorized credential and these values to the configuration example only if this is your intended service. This is historical evidence, not a current account check.
Save the enabled model connection ID, choose the exact Harness and a verified Sandbox combination, then use the first Session programs with that selection. Keep their persistent journal, artifact-content checks, close and retention checks intact. Run both clients independently. The November 20 first-Session evidence uses a different configured Messages endpoint and does not prove this Chat configuration was rerun by that tutorial.