stripe-projects

E2B Stripe Projects

Use these patterns after E2B sandbox/API access has been provisioned through Stripe Projects.

Credentials

• Stripe Projects provisions E2B sandbox/API access and returns an E2B team API key.
• Use that key as E2B_API_KEY for sandbox creation, sandbox control, and SDK clients.
• Prefer setting E2B_API_KEY explicitly in runtime environments so commands and SDK calls use the intended E2B team.
• Local defaults can also come from .env.local or ~/.e2b/config.json.
• In Stripe Projects checkouts, the E2B CLI may not be globally logged in. Before using e2b sandbox ..., prefer a Stripe Projects env pull plus per-command export instead of trying e2b auth login.
• Do not print secret values. stripe projects env --json can return redacted placeholders, so do not use it as the source for a runnable E2B_API_KEY. Pull the managed env file, then read only the needed E2B variables into the command environment without echoing them.

stripe projects env --pull --yes
env_value() {
  awk -F= -v key="$1" '$1 == key {sub(/^[^=]*=/, ""); gsub(/^"|"$/, ""); print; exit}' .env
}
export E2B_API_KEY="$(env_value E2B_API_KEY)"
export E2B_API_URL="$(env_value E2B_API_URL)"
export E2B_DOMAIN="$(env_value E2B_DOMAIN)"
e2b sandbox create base --detach

Stripe Projects CLI

Add E2B to the current Stripe project:

stripe projects add e2b/sandboxes

Inspect or pull provisioned credentials:

stripe projects env
stripe projects env --json
stripe projects env --pull --yes

Export the E2B API key before using the E2B CLI or SDK. Prefer stripe projects env --pull --yes for command execution because JSON output may redact secret values. Read only the variables you need from .env; do not source .env as shell code:

stripe projects env --pull --yes
env_value() {
  awk -F= -v key="$1" '$1 == key {sub(/^[^=]*=/, ""); gsub(/^"|"$/, ""); print; exit}' .env
}
export E2B_API_KEY="$(env_value E2B_API_KEY)"
export E2B_API_URL="$(env_value E2B_API_URL)"
export E2B_DOMAIN="$(env_value E2B_DOMAIN)"