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

Cloudflare Sandbox

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 valuecloudflare
Create inputNo provider-specific create options
Connection fields1

Create options

Wildflower rejects provider-specific create options for this adapter instead of silently ignoring them.

Runtime behavior

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

Image selectionfixed
Timeoutprovider managed
Output streamsseparate
Working directorySupported
Environment variablesNot supported
Persistent resumeSupported
Explicit stopNot supported
Snapshots / restoreNot supported
DeleteSupported

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
bridgeUrlX-Provider-Bridge-Url
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 analytics api
Wildflower integrationadditional credentials required
Provider granularityinstance
Expected laganalytics pipeline delay
Provider-reported costUnavailable
Live credential proofNot verified
Cloudflare Sandbox provider cost is not available

Cloudflare exposes per-instance usage metrics, but the current bridge contract does not expose the required analytics identity or credential.

  • The current bridge profile stores neither an account identifier nor an Analytics API token.
  • GraphQL usage values estimate billing and are not an invoice.

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

Continue