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

# Sandboxes

Sandbox execution is not available as a released public service in this documentation. The API contract includes sandbox resource records and lifecycle requests. These definitions do not prove that a sandbox can boot or run a command.

The current contract contains these operations. Paths are relative to the API base path.

| Method | Path                               | Contract purpose                 |
| ------ | ---------------------------------- | -------------------------------- |
| GET    | `/sandboxes`                       | List records for a project.      |
| POST   | `/sandboxes`                       | Request creation.                |
| GET    | `/sandboxes/{sandbox_id}`          | Read a record.                   |
| DELETE | `/sandboxes/{sandbox_id}`          | Request deletion.                |
| POST   | `/sandboxes/{sandbox_id}/start`    | Request start.                   |
| POST   | `/sandboxes/{sandbox_id}/stop`     | Request stop.                    |
| POST   | `/sandboxes/{sandbox_id}/snapshot` | Request a snapshot.              |
| POST   | `/sandboxes/{sandbox_id}/restore`  | Request restore from a snapshot. |

Use the current generated API reference for request and response fields. Create uses a project UUID and a `spec` object. Select exactly one registered `image_id` UUID or an immutable OCI `image` reference with a SHA-256 digest. A mutable image tag is not a valid direct create input.

A `202` response means that the request was accepted. It does not mean that the requested action is complete. Read the operation at `/operations/{operation_id}` and check its `state`. Resource state and operation state are separate.

Public command execution, terminal sessions, file transfers, tunnels, policy updates and snapshot fork batches are not available through this contract. SDK helper names do not establish support for these functions.

No public guarantee is made here for VM isolation, image boot, Docker, network enforcement, secret delivery, retained output, filesystem persistence or snapshot consistency. Resource limits in a schema are validation ceilings, not available capacity. This guide gives no launch date or service-level target.