Reference / providers / generated

Runloop

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 valuerunloop

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 selectionblueprint

Timeoutseconds

Output streamsseparate

Working directorySupported

Environment variablesSupported

Persistent resumeNot supported

Explicit stopNot supported

Snapshots / restoreNot supported

DeleteSupported

Maximum: 172,800 seconds. 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 signalno documented api

Wildflower integrationestimate only

Provider granularitynone

Expected lagunknown

Provider-reported costUnavailable

Live credential proofNot verified

Runloop provider cost is not available

Only published resource rates are available to Wildflower.

No public per-devbox usage or cost API is documented for Wildflower to integrate.
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.

Runloop

Create options

Runtime behavior

Connection context

Usage, cost, and latency evidence

Continue