Skip to content
Rayobyte Docs

Overview

The gateway at https://browser.rayobyte.com holds a pool of backend machines, each running a fixed number of browser seats. You ask it for a browser; it picks a machine with a free seat, starts Chromium there, and answers with the address of that browser.

Terminal window
curl -G "https://browser.rayobyte.com/connect" \
  --data-urlencode "os=windows" \
  --data-urlencode "proxy=http://USERNAME:[email protected]:8000" \
  -H "x-api-key: rb_live_YOUR_KEY"

The gateway leaves the data path

Section titled “The gateway leaves the data path”

After that one response, the gateway is out of the way. Your CDP client talks straight to the backend over wss://sb-NN.browser.rayobyte.com/cdp/.... Nothing you send to the browser passes through the gateway again.

Two things follow from that:

  • Gateway restarts do not disturb a running session.
  • A gateway that is up says nothing about whether your browser is still alive. Poll GET /api/browser/:id/status for that, or watch for your CDP socket closing.

The lifecycle

Section titled “The lifecycle”
  1. GET /connect or POST /api/browser/create creates the session. It starts ACTIVE and is given an id of the form br_ plus 16 hex characters.
  2. You drive the browser over CDP. Dropping the CDP connection does not end the session: it keeps running, and reconnecting picks up the same browser with its cookies, storage and open tabs.
  3. It ends in one of three ways, and only these three. You close it (CLOSED), its lifetime runs out (EXPIRED), or it disappears without being asked to go (DEAD).

All three end states are final and all three count toward your 48 browser hours. DEAD included: a browser that died at minute 40 of a 60 minute session bills the 40 minutes it ran. Every session counts for at least 30 seconds.

Reaching any end state frees the concurrency slot immediately.

What runs the browser

Section titled “What runs the browser”

Chromium, patched at the source level by Rayobyte. Each session is assigned a device profile taken from a real device, and more than 50 signals are set in the engine to match it. See Fingerprint spoofing.

Getting an API key

Section titled “Getting an API key”

Sign in to app.rayobyte.com and open Browser then API access. Every Rayobyte account has a key; there is nothing to request and no waiting list.

Next: Authentication and Connecting.

Was this page helpful?