Browsergridby Zyxio
Documentation

Overview

Use the service

Billing

Reference

Overview

Overview

Browsergrid captures web pages, lends you remote browsers and runs your containers, billed from credit or by monthly invoice per published result, browser-hour and vCPU-hour.

What you can do

  • Captures. Send up to 1,000 URLs in one batch. 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.
  • Browser sessions. Lease a remote Chromium for up to four hours and drive it over the Chrome DevTools Protocol from Playwright, Puppeteer or any CDP client. See Browser sessions.
  • Analytical jobs. Run a linux/amd64 container image with the CPU and memory you choose, then read its output. See Analytical jobs.
  • MCP. Give an AI agent all of the above 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 Zyxio, using GitHub or Google. Accounts are by invitation; the first sign-in with an invitation link creates your account.
  • 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

Everything you create belongs to the identity that created it. 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.

What it costs

ServicePrice
Plain fetch (fetch)€0.12 per 1,000 published results
Browser fetch (browser-fetch)€0.80 per 1,000 published results
Rendered fetch (render-fetch)€0.80 per 1,000 published results
Full capture (capture)€1.00 per 1,000 published results
Browser session€0.07 per browser-hour, accrued per millisecond
Analytical job, CPU€0.04 per vCPU-hour, accrued per millisecond
Analytical job, memory€0.0064 per GiB-hour, accrued per millisecond

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 and an MCP client, in that order.