---
title: "Build against the sandbox boundary."
description: "Documentation for the Wildflower Computer provider-neutral sandbox API and generated TypeScript, Python, Rust, Go, and Zig SDKs."
canonical: "https://wildflower.computer/docs/"
openapi_version: "0.8.0"
source_revision: "788b7325a454b8b753a7d614247d5694bad5c967"
---

# Build against the sandbox boundary.

Wildflower Computer is a provider-neutral sandbox API for 12 supported providers using customer-owned credentials. Use the HTTP contract directly or through a generated SDK.

- [Install and run locally](https://wildflower.computer/docs/installation/) — 01 / Start — Start the API honestly from its current pre-release source.
- [Run a complete lifecycle](https://wildflower.computer/docs/getting-started/) — 02 / Tutorial — Create a sandbox, execute a command, then delete it safely.
- [Connect provider access](https://wildflower.computer/docs/provider-profiles/) — 03 / Guide — Keep customer-owned credentials out of lifecycle payloads.
- [Run commands and transfer files](https://wildflower.computer/docs/commands-and-files/) — 04 / Guide — Work inside one persistent provider sandbox.
- [Retry what you can prove](https://wildflower.computer/docs/reliability/) — 05 / Guide — Use idempotency, reconciliation, and response metadata safely.
- [Refresh documentation locally](https://wildflower.computer/docs/local-ci/) — 06 / Guide — Regenerate SDK facts and pass every gate without hosted CI.
- [Diagnose a failed boundary](https://wildflower.computer/docs/troubleshooting/) — 07 / Guide — Map stable error codes to the next useful action.
- [Understand the boundary](https://wildflower.computer/docs/concepts/) — 08 / Explanation — Learn how IDs, credentials, persistence, and provider selection work.
- [Compare providers](https://wildflower.computer/docs/providers/) — 09 / Reference — See the current supported parameters and execution behavior.
- [Inspect every operation and model](https://wildflower.computer/docs/reference/) — 10 / Generated reference — Browse the exact contract shared by all 5 generated SDKs.

## Current API surface

Every sandbox operation requires the Wildflower Computer bearer key. Provider access comes from a connected project profile or an inline credential override.

| `GET` | [/v1/sandboxes](https://wildflower.computer/docs/reference/list-sandboxes/) | List project sandboxes |
| --- | --- | --- |
| `POST` | [/v1/sandboxes](https://wildflower.computer/docs/reference/create-sandbox/) | Create a persistent running sandbox |
| `GET` | [/v1/sandboxes/{id}](https://wildflower.computer/docs/reference/get-sandbox/) | Get a sandbox |
| `POST` | [/v1/sandboxes/{id}/exec](https://wildflower.computer/docs/reference/run-sandbox-command/) | Run a command in an existing sandbox |
| `POST` | [/v1/sandboxes/{id}/files/read](https://wildflower.computer/docs/reference/read-sandbox-file/) | Read a file from an existing sandbox |
| `POST` | [/v1/sandboxes/{id}/files/write](https://wildflower.computer/docs/reference/write-sandbox-file/) | Write a file in an existing sandbox |
| `DELETE` | [/v1/sandboxes/{id}](https://wildflower.computer/docs/reference/delete-sandbox/) | Delete a sandbox |
| `GET` | [/v1/providers](https://wildflower.computer/docs/reference/list-providers/) | List provider capabilities |

## What is intentionally outside the API

The MVP does not include automatic provider failover, billing, stored provider resale, model execution, or an agent runtime. Those absences are part of the current product boundary, not hidden features.