Skip to main content
Register, upload, and inspect the models and adapters you deploy for dedicated model inference deployments with the 2.0 API. Bringing your own weights is a two-step flow:
  1. create registers a model record (metadata only), then
  2. upload or remote-uploads create adds the weight files.
See Custom models for the end-to-end workflow.
These commands target the 2.0 API. For the 1.0 model commands, see models. Commands run within a Together project.

Create

Register a new model record. This creates metadata only. It does not upload any files. Upload the weights afterward with upload or remote-uploads create.
Shell
You can also pass a base model ID (ml_...). Values that do not start with ml_ are treated as a deploy model name: the CLI searches public supported models and requires an exact match on a deployment profile’s modelName. If the name is missing or matches more than one profile, the CLI prints the candidate model names and ids and asks you to re-run with an exact name or ml_... id. Alias: tg beta models -c.

Parameters

Upload

Upload weight files from your local machine to an existing model or adapter record.
Shell

Parameters

List

List the models in the current project.
Shell
Alias: tg beta models ls.

Parameters

Retrieve

Get a single model by ID.
Shell
Alias: tg beta models get.

Update

Update a model record. Only the fields you pass are changed.
Shell

Parameters

Delete

Delete a model record. This removes the metadata. It does not delete uploaded files.
Shell
Alias: tg beta models -d.

Configs

List the deployable configs for a model. Pass a config ID to tg beta endpoints deploy --config to deploy that specific configuration.
Shell
Pass a bare model ID (ml_...), a resource path (projects/{project_id}/models/{model_id}), or a model name. Names with a / resolve through the private models list when the prefix matches your project slug, or through public supported models otherwise. Ambiguous public names print a short error that points you at tg beta models public --search.

Parameters

List files

List the files in a model or adapter.
Shell

Parameters

List revisions

List the revisions of a model.
Shell

Parameters

Download

Download the weight files of a model or adapter to a local directory.
Shell

Parameters

List public models

List the publicly visible models across all projects. Use this to find a base model ID or deployment profile modelName for create and tg beta endpoints deploy.
Shell
The human-readable table prints one row per deployment profile, with columns for Model (the profile’s modelName, such as Qwen/Qwen3.5-9B-FP8), GPUs, and Parallelism. Pass that Model value as the MODEL argument to tg beta endpoints deploy when you want that specific profile. Add --json to see each architecture’s full record, including its id (which subsequent operations require) and its deploymentProfiles array. A model can expose more than one profile, each pairing a certified config with a hardware and parallelism choice, so read the profile’s modelName, config, gpuType, and gpuCount before deploying. See Choose a hardware config.

Parameters

List org models

List the internal-visibility models in your organization.
Shell

Parameters

Remote uploads

Import model weights server-side from a Hugging Face repo or a presigned S3/GCS URL, without downloading them locally first. Create a remote upload job against an existing model record, then poll it until it succeeds.

Remote uploads create

Start a remote upload job.
Shell
For gated or private Hugging Face repos, pass a source credential with --token. For S3 or GCS, pass a presigned archive URL as --from (no token needed).

Parameters

Remote uploads retrieve

Get a remote upload job by ID. Poll this until status is REMOTE_UPLOAD_STATUS_SUCCEEDED.
Shell

Parameters

Remote uploads list

List remote upload jobs.
Shell

Parameters

Global options

Every command also accepts the global parameters, including --json for machine-readable output and --project to override the target project.

Resource IDs