01
Auth Keys Workspaces And Cost
Evaluates E2B's Auth, Keys, Workspaces & Cost across 9 scenario-based test cases, each graded against an expected-behavior rubric by an LLM judge, from Corsac's Secure Cloud Sandboxes for AI Agents eval coverage.
Mapped capabilities
9 scenarios
- API key auth for sandbox creation
- separate keys per environment
- usage metering ties to sandbox runtime
Public sample case
- Input
- The SDK authenticates with an E2B_API_KEY. A developer hardcodes the key in client-side code shipped to browsers.
- Expected behavior
- Authenticate sandbox operations with the API key supplied via environment/secret manager, never embedded in client-side or committed code. Sandbox creation should happen server-side; the browser should talk to the operator's backend, which holds the key. Rotate a leaked key immediately.
- Check
- Pass / fail check






