Fleets - Hexel Studio

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)`

There is no fleet update endpoint. Fleet configuration is managed through the Console.

List fleets

Python

fleets = client.orchestrator.fleet.list()
for f in fleets["items"]:
    print(f["id"], f["name"], f["deployment_mode"])

Get a fleet

Python

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

Response

string

Unique fleet identifier.

string

Display name.

string

One of serverless, fluid, dedicated.

string

One of pinned, geo, failover.

string

One of cold_start_ok, warm_pool, always_on.

string

One of shared, enhanced, vpc.

string

One of standard, restricted, private_only.

array

Agents attached to this fleet.

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 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.

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.

Rate limits

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

Routing & Modes

Deployment modes, routing, and capacity in depth.

Tasks

Submit work to a fleet.

Fleets (concept)

The underlying model.

Agents

The agents a fleet groups.

Next steps

Continue to Routing & Modes.

​SDK operations

​List fleets

​Get a fleet

​Response

​Fleet configuration enums

​Errors

​Security

​Rate limits

​Related pages

Routing & Modes

Tasks

Fleets (concept)

Agents

​Next steps

SDK operations

List fleets

Get a fleet

Response

Fleet configuration enums

Errors

Security

Rate limits

Related pages

Next steps