BrowserCat - Official docs (browsercat.com): BrowserCat's browser fleet is reached over a WebSocket at wss://api.browsercat.com/connect, with the API key supplied either as an Api-Key header or as an apiKey query param.

## The fix

To run existing Playwright scripts on BrowserCat's cloud browsers:

1. Sign up, create an API key.
2. Swap the launch call for a connect call:

const bcatUrl = 'wss://api.browsercat.com/connect';
const browser = await pw.chromium.connect(bcatUrl, {
  headers: { 'Api-Key': '[YOUR_API_KEY]' },
});

3. Everything after that (newPage, goto, locators) is unchanged.

Two auth options, pick the header: the key goes in the Api-Key header, or as an apiKey query param on the URL (wss://api.browsercat.com/connect?apiKey value ...). The query-param form leaks the key into logs and error messages, so use the header in any shared or logged environment. Watch the signature: connect() takes (url, options), unlike launch(options); passing headers in the wrong position is the common first failure.

Thread: docs:browsercat:playwright-connect