https://api.compute.anonalabs.com
Most users never call it directly: the E2B SDK, the Anona extras and the CLI do. Two groups of routes:
Both files are checked against a running gateway: every operation is called and each answer’s status and body are validated against the spec.
Authentication
Send your API key in theX-API-Key header, or as Authorization: Bearer ac_…:
api_auth.sh
/v1/api-keys routes accept only dashboard sessions; manage keys in the dashboard. Changing the team network settings and the credential vault needs an owner or admin session, or an unrestricted API key (no scopes and no sandbox list). Other API keys can read them, unless they have a sandbox list.
Errors
Errors have the E2B shape, so the SDKs raise their usual exceptions:requestId is also sent as the X-Request-Id header. Quote it when you report a problem. A refusal at a plan limit also says which limit (limit_name), the limit, what is in use now (current) and your plan; see limits.
Service status
status.anonalabs.com shows whether the API, sandboxes, sandbox URLs, the dashboard and these docs are up.GET https://api.compute.anonalabs.com/statusz answers the same question for a script. It needs no API key, answers 200 whenever the API can answer at all, and puts the verdict in the body. The result is cached for 15 seconds.
status is operational, degraded or down, and the top-level status is the worst of the components. sandbox_engine.state is awake, asleep, waking, going_to_sleep or unknown. An engine that is asleep is working as designed: the next create starts it, and that create takes longer. A request that gets no answer at all, or a 5xx, means the API itself is down.
Sandbox traffic
Commands, files and terminals do not go to the API host. They go to the sandbox’s ownenvd at https://49983-<sandbox id>.sbx.compute.anonalabs.com (Connect RPC, E2B’s envd protocol), with the sandbox’s access token from the create response. Live view and SSH use wss://stream.compute.anonalabs.com.