Back to Blog
GuidesJan 15, 20254 min read

Getting Started with Browserize

Learn how to spin up your first virtual browser in under 60 seconds. No Docker, no xvfb, no headaches.

Munashé Sydney

Virtual browsers are the backbone of modern web automation — AI agents browse the web, scrapers extract data, and testing frameworks validate UI. But setting up a browser infrastructure has always been a pain: Dockerfiles, xvfb dependencies, VNC configuration, networking...

Browserize eliminates all of that. You get a fully-managed, cloud-hosted browser in one API call. This guide walks you through your first deployment.

Step 1: Get Your API Key

Head to your project dashboard and generate an API key. Keys are scoped to a single project and grant full access to all browser operations. Keep them secure — treat them like passwords.

Step 2: Create a Browser

With your API key ready, creating a browser is a single POST request:

curl -X POST https://browserize.com/api/v1/browsers \
  -H "Authorization: Bearer sk-brz-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{"name": "my-first-browser"}'

That's it. The API returns a browser ID immediately. Behind the scenes, your browser is being provisioned on our edge network and will transition through Starting Running automatically.

Step 3: Connect and Automate

Once running, you can connect via CDP (Chrome DevTools Protocol) using Playwright or Puppeteer:

import { chromium } from "playwright";

const browser = await chromium.connectOverCDP(
  "wss://connect.browserize.com?apiKey=sk-brz-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"
);

const page = await browser.newPage();
await page.goto("https://example.com");
console.log(await page.title());

// Done? Stop the browser to avoid billing
await fetch("https://browserize.com/api/v1/browsers/{id}/stop", {
  method: "PUT",
  headers: { Authorization: "Bearer sk-brz-xxx" },
});

What's Next?

From here you can scale horizontally — create multiple browsers for parallel scraping, attach MCP servers for AI agent tool use, or fine-tune resource limits for performance-critical workloads. Check the full API reference for details on every endpoint.