Skip to main content
Most Chat Completions applications only need a new base URL, API key, and model name. The rest of the request and response handling stays the same.

Before you begin

You need a W&B API key, a task with routing applied, and the task’s W&B entity.
Omit wandb.entity only when the task belongs to the API key’s default entity.

Verify the integration

Return to the task overview after sending a request. Confirm that:
  • the request count increased;
  • the expected model served the request;
  • the saved input and answer look correct.
If the proxy says the task does not exist in a personal entity, add the team name in metadata["wandb.entity"].

Preserve conversation identity

Use the same wandb.thread_id for every request in one conversation. This keeps a conversation on the same model during a gradual rollout and keeps related examples together when preparing data.

Chat Completions details

Learn about streaming, tools, structured output, provider parameters, and request precedence.
Last modified on August 25, 2026