Current evidence
The adapter has deterministic keyless lifecycle contract coverage. It has not completed a current private-staging credential smoke.
Create a Blaxel sandbox
Authenticate to Wildflower Computer with its bearer key and send yourBlaxel API key separately in X-Provider-Api-Key. The adapter also requires X-Provider-Workspace on every lifecycle request.
curl --fail-with-body "$WILDFLOWER_URL/v1/sandboxes" \ -H "Authorization: Bearer $WILDFLOWER_API_KEY" \ -H "X-Provider-Api-Key: $PROVIDER_API_KEY" \ -H "X-Provider-Workspace: $BLAXEL_WORKSPACE" \ -H "Content-Type: application/json" \ --data '{ "provider": "blaxel", "image": "blaxel/base-image:latest", "timeout": 300}'Capabilities and behavior
| Concern | Current behavior |
|---|---|
| Image | The image is a Blaxel runtime image and defaults to blaxel/base-image:latest. |
| Lifetime | An optional timeout in seconds is sent to Blaxel as the runtime TTL. |
| Execution | The adapter returns the provider process stdout, stderr, and exit code through the shared execution result. |
| Credential | Blaxel API key; resolved from a project profile or supplied as an ephemeral inline override. |
Current limitations
- Every create, get, runCommand, and delete request also needs the Blaxel workspace.
- Wildflower Computer does not infer or store workspace routing context.
- A Blaxel sandbox cannot be moved to another provider after creation.
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 Blaxel
- Use the Python SDK with Blaxel
- Use the Rust SDK with Blaxel
- Use the Go SDK with Blaxel
- Use the Zig SDK with Blaxel