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

Blaxel

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 valueblaxel
Create inputimage and timeout
Connection fields1

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 stopNot supported
Snapshots / restoreNot supported
DeleteSupported

Granularity: 1 second.

Connection context

These values identify provider-side workspace or bridge context. They are not credentials and remain separate from the provider API key.

FieldInline header
workspaceX-Provider-Workspace
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 signalprovider billing api
Wildflower integrationadditional scope required
Provider granularityresource
Expected laga few minutes or longer under load
Provider-reported costUnavailable
Live credential proofNot verified
Blaxel provider cost is not available

The provider has a resource-centric Billing Explorer API, but Wildflower requires a separately verified billing scope before querying it.

  • Wildflower does not assume a sandbox lifecycle token has account billing access.
  • Billing data is delayed and is unsuitable for hard real-time enforcement.

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

Continue