E2B ↗
Run your code in an isolated execution environment.
Before you connect
Provision an API key and approve the compute budget.
Our integration playbook
Treat the sandbox lifecycle as part of the task
INFRASTRUCTURE FOR THE AGENT ECONOMY
Code execution services for AI agents
Execute generated code and inspect its result.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
100 available services15 capability categoriesOpen discovery · no login
Choosing code execution for your task
Start with a deterministic smoke check, then capture standard output, errors and expected artifacts. Keep external writes separate from retryable computation.
Before you proceed: A timeout does not prove that a side effect failed to happen.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
Services with Code execution
5 services · Catalog updated 2026-10-27 · See each listing’s review date
Daytona ↗
Provision an isolated cloud computer for your code and tools.
Before you connect
Create a Daytona organization, provision an API key and approve resource usage and billing.
Our integration playbook
Make sandbox cleanup part of your result
Modal Sandboxes ↗
Allocate isolated compute for generated code and custom dependencies.
Before you connect
Create a Modal account and workspace, configure credentials, and authorize the compute budget and any required secrets.
Our integration playbook
Budget the environment before executing generated code
Runloop ↗
Execute coding tasks in managed development sandboxes.
Before you connect
Create a Runloop account and scoped API key; approve repository access, environment inputs and resource spending.
Our integration playbook
Keep environment identity with each coding result
Riza ↗
Run generated code through an isolated code-interpreter API.
Before you connect
Create a Riza account and API key; choose the runtime, input data, permitted network access and spending limit.
Our integration playbook
Use a bounded transformation before executing generated tools
Explore related capabilities
Browse all service tags →NO BROWSER REQUIRED
Discover. Inspect.
Connect.
Search for a capability, then follow the listing’s siteGuide link for our original integration playbook: selection advice, workflow, acceptance checks and recovery steps. The complete playbook is in the page HTML, so you can fetch it without JavaScript or a login.
GET /api/agent-services?capability=email GET /api/agent-services?interface=mcp GET /api/agent-services?payment=x402-wallet GET /api/agent-services?payment=mpp-wallet GET /api/agent-services?payment=no-payment GET /api/agent-services?id=e2b
Full catalog: /data/agent-services.json
Manifest: /.well-known/agent-services.json
Choose your next service with the facts in hand.
Find the tools you need
You are here to get something done. Find a mailbox for your messages, a browser for your web tasks, a sandbox for your code, or a wallet for approved payments.
Check what you need from your owner
Inspect the setup requirements before connecting. You may need your owner to create an account, grant OAuth consent, fund a wallet, or provide a website login.
Confirm your payment path
Check whether usage is free, billed to a provider account or uses a documented x402 or MPP wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.