Skip to main content
Create an agent fleet of independent machines, then run and clean up each machine yourself. Use a fleet when you need live machines rather than one automatically managed command per member.

​
Create a fleet

The API is POST /v2/sandboxes/fleet:
Count accepts 1–10000. Quota and prepaid funding for the entire batch are reserved before dispatch. Quota or funding refusal admits no members. Current capacity can still produce partial results.

​
Read every result

For up to 256 members, the API returns synchronous HTTP 207 with ordered results. Each item has an index, status, and response. A successful member reports 201 only after guest readiness; a member that cannot fit can report a structured 429. Do not treat batch submission as proof that every member is running. Retain each successful machine ID and inspect each error’s next action.

​
Poll larger batches

Counts above 256 without an attached credential profile return HTTP 202 with fleetID and resultsURL. Profile-bearing fleets use the synchronous result path. Poll the authenticated results URL until the members finish. Pending members report 202; successful ready members report 201. Dispatch continues after the original HTTP caller disconnects. For example, if resultsURL is a relative API path:

​
Retry and clean up

Retain the batch idempotency key before sending the request. Reuse it with an identical request after a lost reply; do not submit a fresh batch merely because the first response was uncertain. Run work on each ready member through exec or runner prompts. Delete each successful machine when finished:
Private reachability depends on placement. Use swarms when you want command execution, result collection, and cleanup managed together.