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

Smol Machines

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 valuesmol
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 streamsseparate
Working directorySupported
Environment variablesSupported
Persistent resumeSupported
Explicit stopSupported
Snapshots / restoreNot supported
DeleteSupported

Granularity: 1 second.

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 signalper machine metered usage and cost
Wildflower integrationprovider signal not integrated
Provider granularitymachine
Expected lagprovider-defined
Provider-reported costUnavailable
Live credential proofNot verified
Smol Machines provider cost is not available

Smol documents per-machine metered cost, but Wildflower has not integrated and live-verified that signal; comparable public unit rates are not published.

  • Wildflower has not yet integrated Smol's documented per-machine metered usage and cost signal.
  • The lifecycle adapter response does not prove that every credential can read the metered cost fields.
  • Smol does not publish comparable CPU or memory unit rates, so a normalized list-price estimate is also unavailable.

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

Continue