Overview

Browsergrid captures web pages, lends you remote browsers, runs your containers and provisions managed services, billed from credit or by monthly invoice.

What you can do

• Web Captures. Send up to 1,000 URLs in one batch with POST /batches. Each URL is fetched or rendered in Chromium and published as an immutable set of files: a screenshot, the rendered HTML or the raw body, and a metadata record. See Captures.
• Remote Browser Sessions. Lease a remote Chromium with POST /sessions for up to four hours and drive it over the Chrome DevTools Protocol from Playwright, Puppeteer or any CDP client. See Browser sessions.
• Browser Overview with the jev decision model. Crawl your site with the Site-QA runtime as an analytical job, at the job prices: jev judges each rendered page and the sitemap's coherence, and the job reports SARIF 2.1.0 and JUnit XML; see Analytical jobs. AI agents get a Browser Overview of up to 20 routes, with per-route verdicts, a sitemap coherence score and layout issues, from the browsergrid-browser MCP server's browser_site_overview tool, charged as the browser session it drives. Per-URL route audits with POST /audits are coming.
• Burst Compute & Actions Runners. Run a linux/amd64 container image as an analytical job with POST /jobs, with the CPU and memory you choose, then read its output; see Analytical jobs. Actions runners with 2 or 4 vCPU, priced per runner-minute, are coming.
• Managed Data & AI Services. Provision PostgreSQL + PgBouncer, MLflow, LiteLLM or Valkey / Redis from your managed services or POST /managed-services/instances, in five size tiers with 1 to 8 replicas. See Managed services.
• Managed Web App Hosting, coming: a webapp instance that serves a linux/amd64 container image pinned by its @sha256: digest, in the same tiers.
• MCP. Give an AI agent captures, browser sessions and analytical jobs as tools. See MCP.

The endpoint

Every API call goes to https://grid-lab.zyxio.xyz. Your panel and these pages live on a host of their own, under https://console.grid.zyxio.xyz/run; the panel shows the endpoint with a copy button.

Signing in and authenticating

• The panel (/run/app): sign in with your email address and the 6-digit code we email to it. New accounts wait for operator approval before you can sign in (see Credit and billing). An invitation can create an account or add you to a team.
• API calls: send an API key in the x-api-key header. You create keys on the panel; see API keys.
• MCP clients can sign in with Zyxio instead of using a key; they send the resulting token as Authorization: Bearer.

Who can see what

Captures, jobs, artifacts and sessions belong to the identity that created them. Asking for someone else's batch, job, artifact or session gives the same 404 as asking for one that does not exist.

All API keys of your account act as one identity, so a new key sees everything an older key created. Your Zyxio sign-in is a separate identity: a batch created with a key is not visible to an MCP client signed in with Zyxio, and the other way round. Both are billed to the same account. Managed service instances belong to the account: its identities can list and manage them, while credential downloads and gateway calls also require a grant on the instance.

What it costs

Managed service prices are Tier-1 base plans, the standard tier, prorated per active millisecond of each UTC calendar month. The other four tiers, tiny, starter, pro and scale, have proposed prices, tiny from €2.00 to €3.50 per month depending on the service; until a rate card carries a tier's price, every tier is billed at its service's Tier-1 base price. Each instance takes 1 to 8 replicas; see Managed services.

Failed captures, browser start-up time and failures on our side are free. See Pricing units and Credit and billing.

Next

Follow the Quickstart: a key, a capture batch, a session, a job, a managed service and an MCP client, in that order.