Sanaf AI
Start free
Developer Tools

E2b, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your E2b account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Developer Tools
  • Connects with a key
  • 27 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What E2b is

Open-source Code Interpreting for AI Apps. Run sandboxed code execution environments with support for multiple programming languages.

You paste in a key from your own E2b account. It is kept encrypted, and you can withdraw it from inside E2b whenever you like.

How a run works

One message in, the work done in E2b.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in E2b. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own E2b account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

27 tools it already has

What it can do in E2b

These are the ready-made tools your AI employee already has in E2b. It is not limited to them, but it never has to be taught these.

  • Check API HealthTool to check the health status of the E2B API. Use when you need to verify that the API service is operational and accessible.
  • Connect to SandboxTool to connect to an existing E2B sandbox and retrieve its details. Use when you need to reconnect to a sandbox from different environments or resume a paused sandbox. The TTL is
  • Create SandboxTool to create a new E2B sandbox from a template. Use when you need to launch a fresh sandbox environment for code execution, testing, or development purposes.
  • Create TemplateTool to create a new E2B template with specified configuration. Use when you need to define a new sandbox template that can be used to spawn sandbox environments.
  • Create WebhookTool to register a new webhook to receive sandbox lifecycle events for the team. Use when you need to set up notifications for sandbox lifecycle events such as creation, updates, o
  • Delete SandboxTool to terminate and permanently delete a running E2B sandbox instance. Use when you need to kill a sandbox that is no longer needed. Once terminated, the sandbox cannot be resume
  • Delete WebhookTool to unregister a webhook and stop receiving lifecycle events. Use when you need to remove a webhook that is no longer needed or to clean up webhook registrations.
  • Get SandboxTool to retrieve detailed information about a specific sandbox by its ID. Use when you need to check sandbox status, metadata, or configuration details.
  • Get Sandbox Lifecycle EventsTool to retrieve the latest lifecycle events for a particular sandbox instance. Use when you need to track state changes including creation, pausing, resuming, updates, and termina
  • Get Sandbox LogsTool to retrieve logs from a specific E2B sandbox instance. Use when you need to debug or monitor sandbox execution by viewing its console output and system logs.
  • Get Sandbox MetricsTool to retrieve timestamped CPU, memory, and disk usage metrics for a sandbox. Use when you need to monitor resource usage of a running sandbox. Metrics are collected every 5 seco
  • Get Team Maximum MetricsTool to retrieve the maximum value for a specific team metric in a given interval. Use when you need to check team limits or peak usage, such as maximum concurrent sandboxes allowe
  • Get Team MetricsTool to retrieve timestamped CPU, memory, and disk usage metrics for a team. Use when you need to monitor aggregated resource usage across all sandboxes belonging to a team.
  • Get Template Build StatusTool to get the status of a template build. Use when you need to check the build status of a template that was started asynchronously. Useful in polling loops to monitor template b
  • Get Template FilesTool to get an upload link for a tar file containing build layer files. Use when you need to retrieve or download template build layer files by their hash.
  • Get Webhook ConfigurationTool to retrieve the current webhook configuration for a specific webhook. Use when you need to inspect webhook settings, verify configuration, or check webhook status.
  • List All SandboxesTool to list all running and paused sandboxes associated with your team. Use when you need to view active sandboxes, monitor sandbox state, or retrieve sandbox identifiers for furt
  • List All TemplatesTool to list all available E2B templates for your team. Use when you need to view available templates, retrieve template identifiers, or audit template configurations.
  • List All WebhooksTool to retrieve all registered webhooks for your team. Use when you need to view all webhook configurations, audit webhook settings, or manage multiple webhooks.
  • List Sandboxes MetricsTool to retrieve timestamped CPU, memory, and disk usage metrics for multiple sandboxes. Use when you need to monitor resource usage across multiple sandboxes simultaneously. Metri
  • List Team Sandbox Lifecycle EventsTool to retrieve the latest lifecycle events across all sandboxes associated with the team. Use when you need to monitor sandbox activity, track lifecycle changes, or audit sandbox
  • Pause SandboxTool to pause a running E2B sandbox preserving its filesystem and memory state. Use when you need to temporarily suspend a sandbox while maintaining its state for later resumption.
  • Refresh SandboxTool to refresh an E2B sandbox and extend its time to live. Use when you need to keep a sandbox alive longer and prevent it from timing out.
  • Set Sandbox TimeoutTool to set the timeout for an E2B sandbox. Use when you need to extend or reduce the sandbox lifetime. The timeout is measured from the current time, and calling this multiple tim
  • Start Template BuildTool to start a build for an E2B template. Use when you need to initiate the build process for a template with specific configuration. The build runs asynchronously and returns imm
  • Update TemplateTool to update an E2B template configuration. Use when you need to modify template settings such as changing visibility (public/private status).
  • Update Webhook ConfigurationTool to update an existing webhook configuration including URL, enabled status, and subscribed events. Use when you need to modify webhook settings, change the destination URL, ena
Access, and who is in charge of it

You stay the boss of your E2b account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own E2b account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in E2b is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in E2b and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about E2b

Can an AI employee really work inside E2b?
Yes. It signs in to your own E2b account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of E2b?
No. Nothing moves and nothing is replaced. Your records stay in E2b, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my E2b account?
You paste in a key from your own E2b account. It is kept encrypted, and you can withdraw it from inside E2b whenever you like. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in E2b?
It has 27 ready-made tools in E2b today, among them Check API Health, Connect to Sandbox and Create Sandbox. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use E2b and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in E2b and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in E2b?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in E2b is written down with what it did and when.