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 e2b_…:
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 (API keys can read them).
Errors
Errors have the E2B shape, so the SDKs raise their usual exceptions: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.