Current evidence
The adapter has deterministic keyless lifecycle contract coverage. It has not completed a current private-staging credential smoke.
Create a E2B sandbox
Authenticate to Wildflower Computer with its bearer key and send yourE2B API key separately in X-Provider-Api-Key. No additional provider routing header is required.
curl --fail-with-body "$WILDFLOWER_URL/v1/sandboxes" \ -H "Authorization: Bearer $WILDFLOWER_API_KEY" \ -H "X-Provider-Api-Key: $PROVIDER_API_KEY" \ -H "Content-Type: application/json" \ --data '{ "provider": "e2b", "image": "base", "timeout": 300}'Capabilities and behavior
| Concern | Current behavior |
|---|---|
| Image | The image field is interpreted as an E2B template ID. It defaults to base when omitted. |
| Lifetime | The timeout is a sandbox lifetime in seconds and defaults to 300 when omitted. |
| Execution | The adapter preserves separate stdout and stderr streams and returns the command exit code. |
| Credential | E2B API key; resolved from a project profile or supplied as an ephemeral inline override. |
Current limitations
- The image value is a template ID, not a general container image.
- The sandbox remains attached to E2B for its complete lifecycle.
- Wildflower Computer does not migrate E2B filesystem state to another provider.
Tested compatibility
The adapter tests pin the request and response shapes used by Wildflower Computer. These labels describe the tested upstream contract; callers do not select a provider API version.
Use a generated SDK
Every generated client exposes the same lifecycle and typed provider creation inputs. The packages are generated from the versioned OpenAPI document and source model.
- Use the TypeScript SDK with E2B
- Use the Python SDK with E2B
- Use the Rust SDK with E2B
- Use the Go SDK with E2B
- Use the Zig SDK with E2B