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

AWS AgentCore

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 valueagentcore
Create inputtimeout
Connection fields1

Create options

The generated create input exposes these provider-specific fields:

  • timeout

Runtime behavior

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

Image selectionfixed
Timeoutseconds
Output streamsseparate
Working directorySupported
Environment variablesSupported
Persistent resumeSupported
Explicit stopNot supported
Snapshots / restoreNot supported
DeleteSupported

Default: 900 seconds. Maximum: 28,800 seconds. 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
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 telemetry
Wildflower integrationadditional credentials required
Provider granularitysession
Expected lagup to 60 minutes for resource telemetry
Provider-reported costUnavailable
Live credential proofNot verified
AWS AgentCore provider cost is not available

AgentCore exposes usage telemetry, not an authoritative per-session invoice amount through the sandbox lifecycle API.

  • The current bridge credential does not grant Wildflower CloudWatch access.
  • AWS states that observability telemetry can differ from authoritative billing.

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

Continue