rbox developer resources

Use the rbox CLI for workspace automation. The hosted sync protocol is an implementation detail used by the CLI, while the public release endpoints documented in OpenAPI are stable and unauthenticated.

Agent and CI setup

Follow the Agents & CI guide to create an expiring RBOX_KEY on an enrolled machine, install the CLI, and pull a workspace into an ephemeral environment. Give each writing agent its own key; a pull-only fleet may share a read-only key. Treat every key as a secret and revoke it with the CLI when its job is finished.

curl -fsSL https://rbox.to/agent.sh | RBOX_KEY=… sh -s -- --workspace=myapp --dir .
rbox setup --workspace=myapp --dir . --daemon --pull-only

Machine-readable resources

• OpenAPI 3.1 specification
• llms.txt product and documentation index
• XML sitemap
• CLI changelog in Markdown

Authentication and API scope

Health, installers, release manifests, and the changelog are public. The workspace-sync API at api.rbox.to requires credentials minted and managed by the rbox CLI; it is not a supported third-party integration surface and may change with the client protocol. rbox does not currently publish webhooks or an MCP server. For automation, call the documented CLI rather than reproducing its encrypted sync protocol.