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

# Fleets

> List and inspect agent fleets and their runtime configuration.

Fleets group agents so orchestration knows where to route work. You set up a fleet once — choosing its deployment mode, routing policy, and capacity profile — and then tasks target that fleet by ID. This means you configure infrastructure concerns in one place rather than per-task.

A fleet is a named group of agents with shared runtime configuration. Tasks are submitted to a fleet, which resolves the agents and settings used to plan and execute the work.

## SDK operations

| Operation   | Method                                    |
| ----------- | ----------------------------------------- |
| List fleets | `client.orchestrator.fleet.list()`        |
| Get fleet   | `client.orchestrator.fleet.get(fleet_id)` |

<Note>
  There is no fleet update endpoint. Fleet configuration is managed through the Console.
</Note>

## List fleets

<Tabs>
  <Tab title="Python">
    ```python theme={"dark"}
    fleets = client.orchestrator.fleet.list()
    for f in fleets["items"]:
        print(f["id"], f["name"], f["deployment_mode"])
    ```
  </Tab>
</Tabs>

## Get a fleet

<Tabs>
  <Tab title="Python">
    ```python theme={"dark"}
    fleet = client.orchestrator.fleet.get("YOUR_FLEET_ID")
    print(fleet["deployment_mode"])    # serverless | fluid | dedicated
    print(fleet["routing_policy"])     # pinned | geo | failover
    print(fleet["capacity_profile"])   # cold_start_ok | warm_pool | always_on
    ```
  </Tab>
</Tabs>

### Response

<ResponseField name="id" type="string">
  Unique fleet identifier.
</ResponseField>

<ResponseField name="name" type="string">
  Display name.
</ResponseField>

<ResponseField name="deployment_mode" type="string">
  One of `serverless`, `fluid`, `dedicated`.
</ResponseField>

<ResponseField name="routing_policy" type="string">
  One of `pinned`, `geo`, `failover`.
</ResponseField>

<ResponseField name="capacity_profile" type="string">
  One of `cold_start_ok`, `warm_pool`, `always_on`.
</ResponseField>

<ResponseField name="isolation_profile" type="string">
  One of `shared`, `enhanced`, `vpc`.
</ResponseField>

<ResponseField name="egress_policy" type="string">
  One of `standard`, `restricted`, `private_only`.
</ResponseField>

<ResponseField name="agents" type="array">
  Agents attached to this fleet.
</ResponseField>

## Fleet configuration enums

| Field               | Values                                    |
| ------------------- | ----------------------------------------- |
| `deployment_mode`   | `serverless`, `fluid`, `dedicated`        |
| `routing_policy`    | `pinned`, `geo`, `failover`               |
| `capacity_profile`  | `cold_start_ok`, `warm_pool`, `always_on` |
| `isolation_profile` | `shared`, `enhanced`, `vpc`               |
| `egress_policy`     | `standard`, `restricted`, `private_only`  |

See [Routing & Modes](/docs/orchestration/routing-and-modes) for detailed behavior of each setting.

## Errors

| HTTP  | Message                   | When                                                                       |
| ----- | ------------------------- | -------------------------------------------------------------------------- |
| `400` | `primary_region required` | Creating a fleet without a primary region, or other invalid configuration. |
| `404` | `fleet not found`         | The fleet ID doesn't exist or isn't in your scope.                         |
| `403` | `forbidden`               | Your credentials lack the required fleet permission.                       |

## Security

| Operation        | Required permission |
| ---------------- | ------------------- |
| Create fleet     | `fleet-write`       |
| List / get fleet | `fleet-read`        |
| Delete fleet     | `fleet-delete`      |
| Attach agents    | `agent-assign`      |
| Attach resources | `resource-assign`   |

Fleets are scoped to your organization, workspace, and environment.

<Note>
  Fleets support create, read, list, and delete, plus attaching agents and resources. There is no update endpoint — to change a fleet's configuration, create a new fleet with the desired settings.
</Note>

## Rate limits

100 requests per organization per minute. Pagination: `page` >= 1, `page_size` 1–100 (default 20).

## Related pages

<CardGroup cols={2}>
  <Card title="Routing & Modes" icon="route" href="/docs/orchestration/routing-and-modes">
    Deployment modes, routing, and capacity in depth.
  </Card>

  <Card title="Tasks" icon="list-check" href="/docs/orchestration/tasks">
    Submit work to a fleet.
  </Card>

  <Card title="Fleets (concept)" icon="layer-group" href="/docs/concepts/fleets">
    The underlying model.
  </Card>

  <Card title="Agents" icon="robot" href="/docs/compute/agents">
    The agents a fleet groups.
  </Card>
</CardGroup>

## Next steps

Continue to [Routing & Modes](/docs/orchestration/routing-and-modes).