The management API calls a project a task. API paths start with
/tasks/{alias}, where alias is the proxy model name. See API conventions.Proxy model name
The proxy model name is the model string your application uses, such asticket-classifier. It’s unique within a W&B entity and remains stable as models change. It can differ from the name of the W&B project that stores the project’s traces.
The bare proxy model name always means version 1:
When to create a version
Create a new version when you need to experiment with a different model mix or provider parameters without affecting the application’s current traffic. Each version has an independent routing configuration.Creating a version doesn’t move traffic. A caller reaches it only after changing
model to name@vN.What versions do not copy
A version isn’t a copy of the project. Datasets, fine-tunes, and evaluations remain project-level resources. Dataset queries can select which project version’s traffic to use.Recommended progression
To validate a new version before any production traffic reaches it, follow this progression:- Keep production on the bare proxy model name and version 1.
- Create a new version with the proposed routing.
- Send internal or canary traffic to
name@vN. - Inspect analytics and evaluations.
- Change the application’s configured model only when the new version is ready.
API: Create a project version (POST /tasks/{alias}/versions)
API: Create a project version (POST /tasks/{alias}/versions)
This request creates the next version with its own routing. The response contains the assigned version number.For the complete operation, see Create a task version.