Browserbase through Squiid

What Browserbase is

Browserbase is browser infrastructure for automation. Each session is a real Chrome instance in the cloud that you drive over the Chrome DevTools Protocol with Playwright, Puppeteer or Selenium, with residential proxies, captcha handling, stealth settings, file downloads and persistent contexts that keep a login between runs. Session replay and a live view URL let you watch what the automation actually did, which is the difference between debugging in minutes and guessing for an hour. The Stagehand library sits on top for instruction-driven browsing.

Agents need this because a large part of the web has no API. Checking a supplier's stock page, logging into a dashboard to pull a number, filling a government form, capturing a screenshot for a report, or scraping a site that renders entirely in JavaScript are all browser jobs. Running that browser on your own server means Chrome, fonts, memory limits and an IP that gets blocked; running it on your laptop means it stops when the laptop sleeps. Concurrency is the other constraint: running twenty browsers at once is normal for a scraping job and impossible on a small server.

Why connect it through Squiid

Squiid provisions the Browserbase project and keeps the key, so a browser session that is about to visit an untrusted page is not holding your only credential. Calls go to https://api.squiid.io/v1/browserbase/... with Authorization: Bearer $SQUIID_API_KEY, the SDKs work by pointing their base URL at the gateway (gateway convention), and browser minutes plus proxy bandwidth are metered against prepaid credits at Browserbase's list price on your single monthly invoice.

• One account, one key, one bill, one dashboard. Browserbase sits beside every other service your project uses, on the same invoice and the same credit balance.
• Key custody. Squiid holds the Browserbase credentials. Your code carries SQUIID_API_KEY, so BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID 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 Browserbase 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

• Managed Chrome sessions over CDP
• Proxies, stealth mode and persistent contexts
• Live view and session recordings for debugging
• Browser minutes metered against prepaid credits
• Browserbase list pricing, no markup

How to connect Browserbase

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 BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID
SQUIID_API_KEY=sq_live_xxxxxxxxxxxxxxxxxxxxxxxx

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

Pricing through Squiid

Browserbase charges per browser session minute with additional charges for proxy bandwidth, on plans at the provider's listed price. Squiid passes that through at par: one dollar of prepaid credit is one dollar of Browserbase usage, with no markup and no per-request margin.

Browserbase 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 Browserbase 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 Browserbase account, and nothing persistent is left behind. Squiid never owns your code, your schema or your domain, and the gateway speaks Browserbase'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

Browserbase 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 Browserbase 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.