E2B through Squiid

What E2B is

E2B runs short-lived virtual machines built for AI-generated code. A sandbox boots in well under a second, gives you a filesystem, a terminal, process control and network access through an SDK, and disappears when you are done. Code Interpreter templates come with Python and common data libraries installed, custom templates let you bake in your own dependencies, and sandboxes can be paused and resumed so a session keeps its state between turns. The SDK exposes file upload and download, so an agent can pull a user's spreadsheet into the sandbox, run code over it and copy the result back out.

The reason this exists is simple: you cannot run model-written code on your own server. An agent that analyses an uploaded spreadsheet, renders a chart, runs a test suite it just wrote, or executes a user's snippet needs somewhere isolated with its own filesystem and no access to your production secrets. E2B is that place, and it is why code interpreter features in vibe-coded apps stopped being a security problem. Sandboxes have a timeout you set at creation, and long sessions can be paused so an idle conversation is not paying for an idle VM.

Why connect it through Squiid

Squiid provisions the E2B account and keeps the API key, so the sandbox credential is not sitting in the same environment as the untrusted code you are about to run. Calls go to https://api.squiid.io/v1/e2b/... with Authorization: Bearer $SQUIID_API_KEY, and the official SDKs work by pointing their base URL at the gateway (gateway convention). Sandbox seconds are metered against prepaid credits at E2B's list price, with spend broken out per template so a forgotten long-running sandbox shows up straight away, and the total lands on your single monthly invoice.

• One account, one key, one bill, one dashboard. E2B sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the E2B credentials. Your code carries SQUIID_API_KEY, so E2B_API_KEY, E2B_DOMAIN never land in a repository, a preview deployment or an agent’s context.
• Metering you can see. Every call is counted per service and per day, so you know what E2B costs before the month ends.
• Pause on zero. When prepaid credits run out the gateway stops authorizing usage instead of running up a bill you did not fund.
• One rotation. Rotating the Squiid key cuts off every agent, worker and deployment at once, with no provider key to hunt down.

What you get

• Sub-second Firecracker sandboxes for agent code
• Filesystem, shell and network access over an SDK
• Custom templates with your dependencies preinstalled
• Per-second metering with spend shown per template
• E2B list pricing, no markup

How to connect E2B

One variable replaces the provider credentials this service would normally need. Requests go to the gateway and the official SDKs work by pointing their base URL at it (gateway convention).

# .env
# replaces E2B_API_KEY, E2B_DOMAIN
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

# every request: https://api.squiid.io/v1/e2b/...
# header:       Authorization: Bearer $SQUIID_API_KEY

Pricing through Squiid

E2B charges per second of sandbox runtime based on the vCPU and memory of the template, at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of E2B usage, with no markup and no per-request margin.

E2B has no subscription attached on Squiid today. If a plan is required for a feature you need, it passes through at the provider’s listed price with no Squiid fee.

Squiid adds no markup to provider prices. There is a free plan at $0 a month with a 15% fee when you top up credits, Solo at $19.97 a month with a top-up fee that starts at 8% and falls to 3.5% as your spend grows, Team from $29.97 a seat a month with the same ladder one point lower, and Custom with a rate of 3% or less. Credits are prepaid, so E2B usage stops when the balance reaches zero rather than producing an invoice you did not fund. Auto top-up with a cap keeps production running without handing anyone an open-ended card.

If you leave

Export: images, templates and functions are rebuilt from your source in your own E2B account, and nothing persistent is left behind. Squiid never owns your code, your schema or your domain, and the gateway speaks E2B's own API, so the client change is a base URL. The handover page lists what happens for every provider in the catalogue.

Works with every coding agent

E2B through Squiid is just an HTTP call with a bearer token, so every agentic coding tool can use it with the single key already in your environment:

• Claude Code
• Cursor
• ChatGPT
• Codex
• Grok
• Gemini CLI
• GitHub Copilot
• Windsurf
• Perplexity
• Devin
• Replit
• v0
• Lovable
• Cline

Vibe coding a feature on E2B usually means asking for it in plain language and letting the agent write the integration. Because the key is Squiid’s rather than the provider’s, it can do that without ever holding a credential that could be leaked, logged or committed.