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

Reference / providers / generated

Daytona

This reference is generated from the same provider capability model used by every Wildflower SDK. It describes the portable create surface and the non-secret connection context kept separate from provider credentials.

Contract valuedaytona
Create inputimage and timeout
Connection fields0

Create options

The generated create input exposes these provider-specific fields:

  • image
  • timeout

Runtime behavior

These capability facts come from the same generator-owned model used by the provider catalog and SDK documentation.

Image selectioncontainer
Timeoutseconds
Output streamscombined
Working directorySupported
Environment variablesSupported
Persistent resumeNot supported
Explicit stopNot supported
Snapshots / restoreNot supported
DeleteSupported

Granularity: 60 seconds.

Connection context

This adapter needs no additional non-secret connection fields. Its provider credential is still connected separately or supplied as an inline override.

Credentials never enter the create body

Connect the provider once for the project, or send a typed inline credential override. Wildflower keeps credentials in authentication headers and never serializes them into sandbox JSON.

Usage, cost, and latency evidence

Billing signaldashboard only
Wildflower integrationestimate only
Provider granularitysandbox
Expected lagbilling settlement may lag
Provider-reported costUnavailable
Live credential proofNot verified
Daytona provider cost is not available

Per-sandbox billing details exist in the provider UI but are not returned through the current adapter API.

  • Daytona documents per-sandbox CPU seconds, RAM GB-seconds, disk, and cost in its billing UI, but Wildflower does not have a documented API response for those values.
  • Lifecycle responses do not include metered usage or cost.

Review the official provider signal source. A normalized list-price estimate remains separate from provider reporting and invoice reconciliation.

Continue