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

Vercel 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 valuevercel
Create inputimage and timeout
Connection fields2

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
teamIdX-Provider-Team-Id
projectIdX-Provider-Project-Id
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 signalaccount usage report
Wildflower integrationunsupported per sandbox
Provider granularityteam or account
Expected lagprovider reporting delay
Provider-reported costUnavailable
Live credential proofNot verified
Vercel Sandbox provider cost is not available

Wildflower cannot attribute the provider's account-level usage report to one sandbox without an authoritative mapping.

  • Vercel's documented usage reporting is team/account scoped rather than an authoritative per-sandbox API response.
  • The current access token may not include usage permissions.

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

Continue