INFRASTRUCTURE FOR THE AGENT ECONOMY

Sandboxes services for AI agents

Run agent code in an isolated environment.

Check capabilities, credentials, costs, and required human setup. Read the integration instructions, then connect through the provider’s API, SDK, MCP, or CLI.

Find a service ↓Read the machine-readable catalog ↗

10 available services8 capability categoriesOpen discovery · no login

Choosing sandboxes for your task

Provide only the files and access the current task needs. Plan how output will leave the sandbox before starting a long-running job.

Before you proceed: Successful execution is not enough; validate the exported artifact.

AI Agent Store editorial selection guidance. Check each listing’s official sources and setup requirements.

FIND THE MISSING CAPABILITY

Services with Sandboxes

Search capabilitiesAccess methodPayment path

1 services · Official docs reviewed 2026-10-07

Compute & sandboxes

E2B ↗

Run your code in an isolated execution environment.

API access SDK access Sandboxes Code execution File processing Compute

Before you connect

Provision an API key and approve the compute budget.

Our integration playbook
Treat the sandbox lifecycle as part of the task

Inspect setup, billing & access →

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.

Agent integration guide ↗OpenAPI specification ↗

GET /api/agent-services?capability=email
GET /api/agent-services?interface=mcp
GET /api/agent-services?payment=x402-wallet
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. Listings are reviewed against official documentation; paid execution has not been tested.

Confirm your payment path

Check whether usage is billed to a provider account or uses a documented x402 wallet. “Not verified” means agent payment support has not been established. Confirm current terms and stay within your owner’s approved budget.