Deploy
Deploy a model to a new endpoint. If you pass the name or ID of an existing endpoint to--endpoint, the model deploys to that endpoint; if you pass a new name, the CLI creates the endpoint first, then deploys. The model is passed as the positional MODEL argument.
Shell
deploy returns an error that lists the available profiles. Re-run with --config <cr_...> to pick one. When a model has a single profile, the CLI selects it automatically. The CLI defaults --min-replicas and --max-replicas to 1, which may differ from the raw API defaults.
Parameters
List
List endpoints in the current project.Shell
Parameters
Get
Print details for an endpoint or deployment. Pass an endpoint ID (ep_...) to see its deployments and traffic split, or pass a deployment ID (dep_...) to inspect that deployment directly.
Shell
--json, endpoint responses expose deployment state under deployments[].state, while deployment responses expose it under status.state.
Update
Update a deployment’s parameters: rename it, change its replica bounds, adjust autoscaling, set its share of endpoint traffic, or toggle LoRA loading. Pass the deployment ID (dep_...)—the CLI resolves its parent endpoint automatically. At least one option must be set.
Shell
Parameters
LoRA loading can’t be changed after a deployment is created. To turn LoRA on or off, redeploy the model with
deploy --enable-lora.Delete
Delete an endpoint, deployment, A/B experiment, or shadow experiment. The command infers the resource type from the ID prefix (ep_, dep_, abx_, or exp_).
Shell
tg beta endpoints -d.
Parameters
A/B test
Fork a percentage of an endpoint’s live traffic from a control deployment to a new variant model, then compare the two. See A/B testing for the full workflow.Shell
Parameters
Shadow
Mirror a fraction of an endpoint’s live traffic to a new model without affecting responses returned to clients. See Shadow deployments for details.Shell
Parameters
Global options
Every command also accepts the global parameters, including--json for machine-readable output and --project to override the target project.
The 2.0 endpoint commands operate within a Together project. The CLI reads the project from the TOGETHER_PROJECT_ID environment variable, or you can pass --project on any command. Without either setting, an interactive deploy asks you to confirm the project associated with your API key. In CI, agents, --non-interactive mode, or --json mode, set the project explicitly before deploying.
Shell