E2B sandboxes are now available through Stripe Projects

We're excited to join the Stripe Projects developer preview as a partner.

If you've built anything with AI coding agents, you've run into the same wall: the agent can write the code, but getting it somewhere to run requires a human to step in. You provision infrastructure, generate an API key, name it something like agent-testing-foo-1234, and hope you remember which agent it belongs to when something breaks.

It's a structural gap in how agents interact with the services they depend on. There's no standard protocol for an agent to say "I need a sandbox" and receive authenticated, scoped credentials back without a developer acting as an intermediary every time.

When Stripe brought us in as a partner on the Agentic Provisioning Protocol, the goal was to fix exactly that. Now, the agent can use Stripe Projects to discover, provision, and authenticate a secure E2B sandbox, getting credentials in its environment so it can immediately start running code, without a human touching a dashboard.

Stripe as the trust layer

Stripe Projects acts as the trust authority between developers, their agents, and service providers like E2B. Because Stripe already knows who you are and has your payment method, it can vouch for you to any provider in the network, so provisioning an E2B sandbox becomes a single CLI command:

stripe projects add e2b/sandbox

There's no signup flow and no need to manually retrieve your API keys. The agent runs one command and gets back working credentials.

‍

What this means for credentials in practice

Credentials are delivered as environment variables and synced directly to your environment. When someone joins the team, switches machines, or a new agent session starts, simply run:

stripe projects env --sync

Rotation works the same way. One command issues a new key, revokes the old one, and updates the environment:

stripe projects rotate e2b/sandbox
stripe projects env --sync

Why we co-designed the protocol

Secure, reliable code execution is core to what E2B does, so the credentials and ownership model mattered a lot to us. Resources need to live in the user's own account. Credentials need to be scoped, auditable, and rotatable. Provisioning needs to be deterministic enough that an agent can rely on it.

When Stripe reached out, we saw an opportunity to help get this right. Stripe handles payment via a Shared Payment Token. Your card details never leave Stripe, and E2B never sees them. The whole flow is auditable and repeatable from the CLI.

What agents can do once provisioned

Once an E2B sandbox is provisioned, the credentials are available in the environment and an agent can take it from there with the full E2B SDK: creating and managing sandboxes, executing code, handling long-running tasks, taking snapshots, and managing lifecycle, without any human in the loop. And with E2B's prebuilt templates for OpenCode, Codex, Claude Code, and Amp, they're ready to run right away.

E2B sandboxes run on Firecracker microVMs for kernel-level isolation, support any language or framework, and can run for up to 24 hours. The Stripe Projects provisioning step is the bridge from "I need compute" to "I have a fully authenticated E2B environment."

Getting started

Install the Stripe CLI, run stripe projects init my-app, and select E2B to provision a sandbox.

brew install stripe/stripe-cli/stripe && stripe plugin install projects
stripe login
stripe projects init my-app
stripe projects add e2b/sandbox
stripe projects env --sync

We'd love to hear about what you build with Stripe Projects and E2B. Reach out at hello[at]e2b.dev or tag us on LinkedIn or X. 

We're excited to continue evolving the standard and to work with Stripe on sharing a more official specification soon. 

If you want your platform to integrate with E2B, reach out at hello[at]e2b.dev.