> ## Documentation Index
> Fetch the complete documentation index at: https://docs.baseten.co/llms.txt
> Use this file to discover all available pages before exploring further.

# baseten train capacity

> Manage training GPU capacity

## describe

```sh theme={"system"}
baseten train capacity describe [OPTIONS]
```

Describe the organization's training GPU limits and current usage, per GPU type.

Per-team limits are listed below the organization totals when any are set.

### Options

<ParamField body="-q, --jq" type="TEXT">
  Filter JSON output with a jq expression; implies --output json (or jsonl for streamed commands)
</ParamField>

<ParamField body="-o, --output" type="TEXT" default="text">
  Output format

  One of: `text`, `json`, `jsonl`, `none`
</ParamField>

<ParamField body="--profile" type="TEXT">
  Use a specific stored profile for this command, overriding BASETEN\_PROFILE and the current profile
</ParamField>

<ParamField body="-v, --verbose" type="BOOL">
  Enable verbose logging
</ParamField>

### Examples

Describe training GPU capacity

```sh theme={"system"}
baseten train capacity describe
```

### Filter output with `--jq`

Print the organization's H100 limit

```sh theme={"system"}
baseten train capacity describe --jq '.gpu_capacities[] | select(.gpu_type == "H100") | .limit'
```

### Output

**Text mode (`--output text`):** An organization table with columns: GPU TYPE, IN USE, LIMIT, BASELINE, then a per-team table with a leading TEAM column when teams have limits set.

**JSON mode (`--output json`):** payload type `managementapi.GetTrainingGpuCapacityResponse`.

## update

```sh theme={"system"}
baseten train capacity update [OPTIONS]
```

Update the maximum concurrent GPUs of one type that a team may use.

The limit is per GPU type, so raising H100 leaves other types alone.

### Options

<ParamField body="--gpu-type" type="TEXT" required>
  GPU type the limit applies to (for example H100).
</ParamField>

<ParamField body="-q, --jq" type="TEXT">
  Filter JSON output with a jq expression; implies --output json (or jsonl for streamed commands)
</ParamField>

<ParamField body="--max-gpus" type="INTEGER" required>
  Maximum concurrent GPUs of this type the team may use.
</ParamField>

<ParamField body="-o, --output" type="TEXT" default="text">
  Output format

  One of: `text`, `json`, `jsonl`, `none`
</ParamField>

<ParamField body="--profile" type="TEXT">
  Use a specific stored profile for this command, overriding BASETEN\_PROFILE and the current profile
</ParamField>

<ParamField body="--team" type="TEXT" required>
  Team name or ID whose limit changes.
</ParamField>

<ParamField body="-v, --verbose" type="BOOL">
  Enable verbose logging
</ParamField>

### Examples

Raise a team's H100 limit

```sh theme={"system"}
baseten train capacity update --team research --gpu-type H100 --max-gpus 32
```

### Filter output with `--jq`

Print the applied limit

```sh theme={"system"}
baseten train capacity update --team research --gpu-type H100 --max-gpus 32 --jq '.team_gpu_capacity.limit'
```

### Output

**Text mode (`--output text`):** On success, prints the team, GPU type, and new limit to stderr; no stdout output.

**JSON mode (`--output json`):** payload type `managementapi.PatchTeamTrainingGpuCapacityResponse`.