CapabilitiesWays to drive it
Documented HTTP API
A documented web API that any language can call.
Short answer: 12 of 16 providers offer it fully: Agent 37, Blaxel, Boat, Daytona, E2B, InstaBox, Lizard, Morph, Runtime, Sandboxer, Sprites and Tensorlake. Checked 29 October 2026.
Who offers it
Part of Ways to drive it, which explains why it matters.
Fully: Agent 37, Blaxel, Boat, Daytona, E2B, InstaBox, Lizard, Morph, Runtime, Sandboxer, Sprites and Tensorlake. Not at all: boxd, Cloudflare Sandbox, Modal and Vercel Sandbox.
- Agent 37Yes
Two HTTPS planes: api.agent37.com and the instance URL.
docs-confirmed “Use the **Sandbox API** to create and manage persistent sandboxes for code, services, and agents.” Source
- BlaxelYes
Every resource has an HTTP API.
pricing-page “HTTP API for every Blaxel resource” Source
- BoatYes
JSON over HTTPS with an OpenAPI file for other languages.
docs-confirmed “The base URL is `https://boat.dev/api/v1`.” Source
- DaytonaYes
A REST service is the entry point for every SDK and the CLI.
docs-confirmed “The API is a NestJS-based RESTful service that serves as the primary entry point for all platform operations” Source
- E2BYes
An OpenAPI-described platform API on api.e2b.app.
docs-confirmed “Complete E2B developer API. Platform endpoints are served on api.e2b.app.” Source
- InstaBoxYes
JSON REST with a published OpenAPI 3.1 document.
docs-confirmed “The full machine-readable description” Source
- LizardYes
REST under /api, documented call by call.
docs-confirmed “POST /api/sandboxes with `template`, `projectId`, `size`, `timeoutMs`, `envs`, `metadata`, `region`, `volumeName`” Source
- MorphYes
An OpenAPI-described devbox API.
docs-confirmed “Start a new instance from a snapshot.” Source
- RuntimeYes
An OpenAPI document describes the HTTP API.
docs-confirmed “The HTTP API is at `https://api.withruntime.com/v1`” Source
- SandboxerYes
REST at sandboxer.com/api/v1, with a second Daytona-compatible API.
docs-confirmed “`https://sandboxer.com/api/v1`” Source
- SpritesYes
A REST API at api.sprites.dev.
docs-confirmed “https://api.sprites.dev/v1/sprites/my-sprite/exec” Source
- TensorlakeYes
A versioned API reference and a published OpenAPI file.
docs-confirmed “Raw OpenAPI schema for the Tensorlake APIs, useful for exact endpoint inspection and client generation.” Source
- boxdNo
Note: The only wire API is gRPC, so a browser or a plain HTTP client cannot call it.
There is no REST or JSON endpoint; TypeScript and Python SDKs wrap gRPC.
docs-confirmed “Raw gRPC access to the boxd public API, for any language with a protoc plugin.” Source
Note: There is no Cloudflare-hosted API to call; you write a Worker and call it yourself.
A reference bridge Worker exists, but you deploy it in your own account.
docs-confirmed “You deploy the Worker in your account; it is not a Cloudflare-hosted shared API.” Source
- ModalNo
Note: The documented interface is the SDK and its gRPC connection; there is no separate HTTP API to call.
Modal's client libraries are the API surface.
inferred “sb = modal.Sandbox.create(app=sb_app)” Source
Note: Sandbox is driven through the SDKs and the CLI; no HTTP API is documented.
The overview names the CLI, JS SDK and Python SDK as the ways to manage sandboxes.
docs-confirmed “Manage sandboxes through the CLI, JS SDK, or Python SDK.” Source
Related
Need several capabilities at once? Add more in the capability finder. Something wrong here? Use the report link at the bottom of the page.