Providers - CoreWeave Docs

A provider stores one OpenAI-compatible API base URL and its credential for a W&B entity. Routing, relabeling, evaluations, and Automation refer to models through {provider}/{model}.

Register a provider

Open the entity menu, choose Providers, and enter:

Name: Lowercase identifier used in every model reference, such as openai or openrouter.
Base URL: The exact OpenAI-compatible API root, including any required path prefix such as /v1, without query parameters or embedded credentials.
API key: Encrypted before storage and never returned.

Hosted providers are published to the Cloudflare proxy asynchronously. A provider is ready for routed requests when its deployment is Applied at the current revision.

API: Register a provider (PUT /providers/{provider})

The provider name is the last URL segment. This example registers openai:

curl --request PUT \
  --url "https://distillation.training.wandb.ai/v1/providers/openai" \
  --header "Authorization: Bearer $WANDB_API_KEY" \
  --header "Wandb-Entity: your-team" \
  --header "Content-Type: application/json" \
  --data "{
    \"base_url\": \"https://api.openai.com/v1\",
    \"api_key\": \"$OPENAI_API_KEY\"
  }"

Poll GET /providers/openai until its deployment is applied. See Create or rotate a provider.

Studio uses POST /responses for the openai provider so relabeling and evaluations preserve OpenAI reasoning and tool-call behavior. Other providers must implement the OpenAI-compatible POST /chat/completions endpoint.

Enable model IDs

Expand a provider’s model list to:

enable or disable known models in Studio selectors;
add a custom model ID exposed by that provider;
set optional input and output prices in USD per million tokens.

Enabling a model changes Studio discoverability, not runtime permission. Existing routing references remain callable even when a catalog entry is disabled.

Built-in `wandb-inference`

Every entity has a system provider named wandb-inference. It uses the caller’s W&B key rather than storing another credential. Use it for W&B-hosted catalog models and fine-tuned artifacts. You can explicitly register the same name to replace passthrough behavior with a stored credential. Deleting that override restores the system provider on its next use.

Rotate or delete a provider

Submitting the provider form again rotates its URL or key and publishes a new revision. Referencing routes and evaluations continue to use the provider name. Deletion is blocked while the provider is referenced by routing, relabeling, or evaluation configuration. Remove those references first so a live task cannot be stranded silently.

​Register a provider

​Enable model IDs

​Built-in wandb-inference

​Rotate or delete a provider

Register a provider

Enable model IDs

Built-in `wandb-inference`

Rotate or delete a provider