Skip to content
Rayobyte Docs

rayobrowse - a Stealth Chromium Browser

rayobrowse is a stealth Chromium browser that runs on Rayobyte infrastructure. You ask for a browser with one HTTP call and get back a CDP WebSocket URL to drive it with.

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 response body is the URL and nothing else:

wss://sb-02.browser.rayobyte.com/cdp/br_5d4d8610784e2a91

Hand that to Playwright, Puppeteer or anything else that speaks the Chrome DevTools Protocol. Your automation code does not change.

Why a stealth browser

Section titled “Why a stealth browser”

Stock Chromium driven by Playwright or Puppeteer is flagged on its first page load by any site that scores its traffic. navigator.webdriver is set, and the GPU, fonts and screen describe the server it runs on rather than a person’s computer. If the browser is blocked, nothing downstream in a scraper or an agent runs.

rayobrowse is Chromium patched at the source level. Fingerprint values are set in the engine’s C++ code, below anything a page’s JavaScript can inspect, so there is no injected script for a detector to find. Every session draws a device profile taken from a real device, and more than 50 signals agree with it and with each other, down to canvas output, text measurements and the WebGL parameter table. Android profiles are available alongside Windows, macOS and Linux.

Rayobyte’s own Scraping API renders pages with this browser at billion-page-per-month scale.

What you get

Section titled “What you get”

Every account includes 5 concurrent browsers and 48 free browser hours. To raise either limit, email [email protected].

Browser hours are counted from launch to close, summed across every session you have ever run. The cap is a lifetime total, not a monthly allowance. Full detail on Limits.

A proxy is required on every launch

Section titled “A proxy is required on every launch”

There is no launch without a proxy. Send none and the call returns 400 with the code PROXY_REQUIRED. The proxy’s form is checked before a browser is created, so a malformed string costs nothing.

In the dashboard the field arrives pre-filled with your Rayobyte residential proxy and a fresh sticky session id, so the first launch works without typing anything. See Proxy support.

Two ways in

Section titled “Two ways in”

One HTTP call

GET /connect creates the browser and answers with the CDP URL. No SDK, no client library, works from curl.

Quickstart →

The SDKs

Python and Node.js wrappers that add reconnection, live-view URLs and typed errors on top of the same endpoint.

SDKs →

Start here

Section titled “Start here”
  1. Quickstart: a running browser in about two minutes
  2. Authentication: where your rb_live_ key lives
  3. Connecting: every parameter /connect takes
  4. Limits: concurrency, browser hours, and what each error means

Was this page helpful?