E2B ↗
Run your code in an isolated execution environment.
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
Read, transform and produce files during an agent task.
Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.
Specify input formats and the output artifact you expect. Validate the result outside its execution environment before handing it to another worker.
Before you proceed: Keep diagnostics when a conversion produces an empty or unreadable file.
AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.
FIND THE MISSING CAPABILITY
12 services · Catalog updated 2026-10-27 · See each listing’s review date
Run your code in an isolated execution environment.
Provision an API key and approve the compute budget.
Our integration playbook
Treat the sandbox lifecycle as part of the task
Provision an isolated cloud computer for your code and tools.
Create a Daytona organization, provision an API key and approve resource usage and billing.
Our integration playbook
Make sandbox cleanup part of your result
Turn complex documents into text and structured data your agent can inspect.
Create an account, provision an API key and approve uploading the documents and using processing credits.
Our integration playbook
Validate the difficult page before processing the whole collection
Run generated code through an isolated code-interpreter API.
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
Keep agent-generated files in managed object storage.
Create a Tigris account, authorize the intended organization and buckets, and choose access and retention settings.
Our integration playbook
Verify the stored object before handing off its link
Upload, transform and deliver managed media assets.
Choose a Cloudinary product environment and authorize access. An agent can provision a temporary Claimable Cloud, but a person must claim it with email verification to retain it.
Our integration playbook
Verify the delivered variant before publishing its URL
Run hosted image, video and audio generation jobs.
Select a fal account or workspace, authorize the connection, fund the required credits and set a permitted model and spending scope.
Our integration playbook
Treat generation as a tracked job with an output contract
Discover and run hosted machine-learning models.
Create a Replicate account and API token, configure billing when required, and choose a model with suitable input requirements, usage rights and a task budget.
Our integration playbook
Track the prediction before deciding whether to retry
Convert files through hosted import, processing and export jobs.
Create an account, choose credits and issue an API key with only the required task scopes. Select formats, engine options and the export destination.
Our integration playbook
Verify the exported artifact before declaring conversion complete
Upload, transform and deliver files through managed APIs and a CDN.
Create a project and obtain its public and secret keys. Choose a plan, configure storage behavior and select the transformations and delivery access the workflow needs.
Our integration playbook
Track upload, storage and delivery as separate states
Generate paginated PDF documents through a hosted rendering API.
Create an account, retrieve the API key and choose a document plan. Prepare HTML and accessible assets, then test the intended rendering pipeline before production generation.
Our integration playbook
Validate page content as well as successful PDF generation
Operate video ingest, streaming and playback through APIs or MCP.
Create an account and select the intended environment, token permissions and billing plan. Decide whether playback must be public or signed before creating assets.
Our integration playbook
Keep video creation, readiness and playback permission distinct
NO BROWSER REQUIRED
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
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.
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.
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.