Sandboxes and compute through Squiid
Isolated environments where agent-written code actually runs: ephemeral sandboxes, serverless GPU and CPU functions, and headless browsers. They exist so untrusted code and long jobs stay off your laptop and out of your web server.
Who needs this
Agents that execute generated code, run data jobs, scrape logged-in pages or render screenshots.
Squiid lists 4 sandboxes and compute services: 0 live today, 1 next up and the rest on the roadmap. Each one is reachable at https://api.squiid.io/v1/<service-slug>/ with the header Authorization: Bearer $SQUIID_API_KEY, and official SDKs work by pointing their base URL at the gateway (gateway convention).
Sandboxes and compute services
Browserbase
Sandboxes and computeHeadless browsers in the cloud for agents that click, fill and scrape
RoadmapProvisioned E2E2B
Sandboxes and computeSecure cloud sandboxes where AI-generated code can actually run
Next upProvisioned
Modal
Sandboxes and computeServerless GPU and CPU compute defined in Python, billed per second
RoadmapProvisioned RPRunPod
Sandboxes and computeOn-demand GPU pods and serverless endpoints at community prices
RoadmapProvisionedWhy connect them through Squiid
One key, not six
Your .env holds SQUIID_API_KEY and nothing else. Squiid holds the provider keys, so nothing sensitive reaches your repository, a preview deployment or an agent’s context window.
One bill, no markup
Usage is metered at the provider’s list price against prepaid credits, and subscriptions pass through at the provider’s price. 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.
Spend that stops
Every call is metered per service in one dashboard, and when credits run out the gateway stops authorizing usage instead of producing a bill you did not fund.
Questions people ask
Which sandboxes and compute services can I use through Squiid?
4 of them: Browserbase, E2B, Modal, RunPod. 0 are live today, 1 is next up, and the rest are on the roadmap. All of them run on the same SQUIID_API_KEY.
Does Squiid mark up sandboxes and compute pricing?
No. Provider usage is billed at the provider’s list price against your prepaid credits, and subscriptions pass through on the monthly Squiid invoice with no fee. Squiid earns from your plan and the percentage taken when you top up credits.
Can Claude Code and Cursor use these through one key?
Yes. Requests go to https://api.squiid.io/v1/<service>/ with an Authorization: Bearer $SQUIID_API_KEY header, and official SDKs work by pointing their base URL at the gateway. Every agent, from Claude Code and Cursor to Codex, Windsurf and Cline, uses the same single variable.
Connect sandboxes and compute in minutes.
One account, one API key and one invoice for every service in this category and the 100+ in the full catalog.