Documentation Index
Fetch the complete documentation index at: https://tbd-6fc993ce-hypeship-scraperly-link.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
Browser spin-up time
Non-standard configuration can affect browser spin-up time. Settings like non-default viewport sizing, extensions, or Profiles may increase the time it takes for a browser to become ready. Standard configuration includes:- Headful and headless browsers
- Stealth mode both enabled and disabled
Connection notes
- CDP connections are meant to be long-lived but may eventually close. Websocket connections typically can remain active for up to 1 hour, after which they may close automatically. Browser sessions themselves are unaffected—reconnect to the same
cdp_ws_urlto continue using the browser. - Browsers persist independently of CDP. Depending on your timeout configuration, it will continue running even if the CDP connection closes. You can reconnect to the same
cdp_ws_urlif you’re unexpectedly disconnected. - We recommend implementing reconnect logic, as network interruptions or lifecycle events can cause CDP sessions to close. Detect disconnects and automatically re-establish a CDP connection when this occurs.
Unsupported Websites
Some websites deploy bot detection aggressive enough that reliable automation isn’t feasible today — even with stealth mode, residential proxies, and persistent profiles. The list below is incomplete and reflects what we’ve seen in practice.Very Hard
Effectively unscrapable at the moment. Expect login walls, rapid CAPTCHA gates, and device-level fingerprinting that doesn’t yield to residential exits or stealth defaults.Hard
Sometimes workable with the right combination of stealth mode, persistent profiles, and residential proxies, but expect frequent friction and rate-limiting.- X (Twitter)
- Amazon