Wildflower Computer
Open console
Browse Documentation

Wildflower Documentation

Search the contract.

Search human guides and generated API references from one index.

View as MarkdownOpen this page as plain textOpen in ChatGPTAsk questions about this pageOpen in ClaudeAsk questions about this pageOpen in CursorSend this page to Cursor chatDownload OpenAPIUse the machine-readable contract

Documentation / current surface

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.

01 / StartInstall and run locally

Start the API honestly from its current pre-release source.

02 / TutorialRun a complete lifecycle

Create a sandbox, execute a command, then delete it safely.

03 / GuideConnect provider access

Keep customer-owned credentials out of lifecycle payloads.

04 / GuideRun commands and transfer files

Work inside one persistent provider sandbox.

05 / GuideRetry what you can prove

Use idempotency, reconciliation, and response metadata safely.

06 / GuideRefresh documentation locally

Regenerate SDK facts and pass every gate without hosted CI.

07 / GuideDiagnose a failed boundary

Map stable error codes to the next useful action.

08 / ExplanationUnderstand the boundary

Learn how IDs, credentials, persistence, and provider selection work.

09 / ReferenceCompare providers

See the current supported parameters and execution behavior.

10 / Generated referenceInspect every operation and model

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.

Wildflower Computer endpoints
GET/v1/sandboxesList project sandboxes
POST/v1/sandboxesCreate a persistent running sandbox
GET/v1/sandboxes/{id}Get a sandbox
POST/v1/sandboxes/{id}/execRun a command in an existing sandbox
POST/v1/sandboxes/{id}/files/readRead a file from an existing sandbox
POST/v1/sandboxes/{id}/files/writeWrite a file in an existing sandbox
DELETE/v1/sandboxes/{id}Delete a sandbox
GET/v1/providersList 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.