Overview
Point Notte at Steel’s CDP endpoint to run your agents against Steel’s hosted browsers. Notte controls the browser through Chrome DevTools Protocol while your code stays unchanged - simply pass Steel’s WebSocket URL into your Notte Session.Prerequisites
- Notte SDK installed with API key configured (Get an API key)
- Steel account and API key (Get Steel API key)
- (Optional) Note that some Steel endpoints require the API key as a query parameter on the WebSocket URL
Quick Start
Use the Steel SDK to create a browser session, extract the WebSocket URL, and pass it to Notte.The exact API and attribute names may vary. Please refer to Steel’s documentation for the most up-to-date information.
Using an Existing Steel CDP URL
If you already have a WebSocket URL from Steel, connect directly:Authentication & Configuration
- API Key: Steel requires an API key to create browser sessions via SDK. If using a raw WebSocket/CDP URL, include any required query parameters (like
apiKey) in the URL. - Browser Settings: Viewport dimensions, headless mode, regions, and timeouts are configured when creating the Steel session (see Steel Sessions docs).
- Network Configuration: If your organization enforces IP allowlists or proxies, configure those on Steel’s side during session creation.
Troubleshooting
- 401 / 403 errors: Invalid or expired Steel token. Regenerate your API key or re-create the session URL
- WebSocket closed: Steel session terminated or timed out. Create a new Steel session
- No targets/pages available: Ensure the Steel session actually launched a page; let Notte navigate first with the Agent
- Connectivity/firewall: Allow outbound WSS connections to Steel’s host
See Also
- CDP Documentation - Local and external CDP patterns
- Session Replay - Record and replay browser sessions
- Proxies - Configure proxy settings for sessions

