Skip to main content
sandbox.rigbox.dev is built on top of the same Rigbox API base (https://api.rigbox.dev/api/v1). It provides a streamlined UI for running AI-generated code in isolated micro-VMs with terminal access, app management, and log streaming. Use this guide as an API map when building your own sandbox-like experience.

​
API Groups

​
Core Rigbox APIs Used by Sandbox

​
App Management APIs Used by Sandbox

​
Log Streaming APIs

Log streaming uses Server-Sent Events (SSE). Set Accept: text/event-stream header and read the response as an event stream.

​
API Key Management

​
Terminal Access

The Sandbox UI provides terminal access to workspaces via WebSocket connections. This uses the shared terminal infrastructure (xterm.js) and connects through the SSH gateway, not through the REST API.

​
Authentication

The Sandbox UI authenticates via session tokens automatically. For programmatic access, use API keys with the Authorization: Bearer rb_... header.

​
Minimal Sandbox-Like Integration Flow

  1. Check capacity with GET /capacity - verify available is true.
  2. Call POST /quick-deploy with your desired template.
  3. Poll GET /workspaces/{id} until status is running.
  4. Call POST /workspaces/{id}/reconcile-apps to ensure apps are created.
  5. List apps with GET /apps?workspace_id={id}.
  6. Stream logs with GET /apps/{id}/logs/stream for real-time output.
  7. Toggle visibility with PUT /apps/{id}/visibility to expose apps publicly.

​
Key Differences from Clawd

For the Clawd-specific API surface, see /clawd-api-surface.