Global options
These flags work with any command:brightdata login
Authenticate with Bright Data. Opens the browser for OAuth by default.
brightdata logout
Clear stored credentials.
brightdata scrape <url>
Scrape any URL using Bright Data’s Web Unlocker. Handles CAPTCHAs, JavaScript rendering, and anti-bot protections automatically.
brightdata search <query>
Search Google, Bing, or Yandex via Bright Data’s SERP API. Google returns structured JSON with organic results, ads, People Also Ask, and related searches. Bing and Yandex return markdown by default.
brightdata discover <query>
AI-powered web discovery. Submit a query with optional intent, and Bright Data finds, ranks, and optionally extracts full-page content for each result.
brightdata pipelines <type> [params...] [options]
Extract structured data from 40+ platforms. Triggers an async collection job, polls until results are ready, and returns the data.
Supported platforms
E-Commerce
E-Commerce
Professional Networks
Professional Networks
Maps, Reviews & Other
Maps, Reviews & Other
brightdata scraper
Build, run, and maintain custom Bright Data Scraper Studio scrapers from the terminal. Each scraper is identified by a Collector ID (a c_* string) that stays stable across runs and self-healing.
brightdata scraper create <url> <description>
Build a scraper from a natural-language description using Bright Data’s AI Agent. Returns a Collector ID.
brightdata scraper run <collector_id> [url]
Run a scraper on one or more URLs and return the data. The CLI tries real-time mode first and falls back to batch mode automatically when a run exceeds the real-time page-load limit.
brightdata scraper heal <collector_id> <prompt>
Fix an existing scraper in place via AI self-healing. The Collector ID does not change. By default, heal stops at an approval gate and returns status: "awaiting_approval" with a preview_result.
brightdata scraper approve <collector_id>
Commit a heal that is awaiting approval, or reject it with --reject.
brightdata status <job-id>
Check the status of an async snapshot job (from --async scrapes or pipeline collections).
brightdata browser
Control a real browser session powered by Bright Data’s Scraping Browser. A lightweight local daemon holds the browser connection open between commands, giving you persistent state without reconnecting on every call.
Global flags
These flags work with everybrowser subcommand:
Subcommands
browser open
browser open
Navigate to a URL. Starts the daemon and browser session automatically if not already running.
browser snapshot
browser snapshot
Capture the page as a text accessibility tree. This is the primary way AI agents read page content - far more token-efficient than raw HTML.Each interactive element gets a Example output:
ref (e.g. e1, e2) that you pass to click, type, fill, and other interaction commands.browser screenshot
browser screenshot
Capture a PNG screenshot of the current viewport.
browser click / type / fill
browser click / type / fill
Interact with elements using their snapshot
ref values.browser scroll
browser scroll
Scroll the viewport or scroll an element into view.
browser get text / get html
browser get text / get html
Get text or HTML content from the page or a specific element.
browser back / forward / reload
browser back / forward / reload
Navigation controls.
browser close
browser close
Close a session and stop its daemon.
Element
ref values (e.g. e1, e3) are re-assigned on every snapshot call. After navigating or clicking, take a fresh snapshot before using refs again.brightdata zones
List and inspect Bright Data proxy zones.
brightdata budget
View account balance and per-zone cost/bandwidth. Read-only.
brightdata config
View and manage CLI configuration.
brightdata init
Interactive setup wizard. Walks through authentication, zone selection, and default configuration.
brightdata skill
Install Bright Data AI agent skills into coding agents (Claude Code, Cursor, Copilot, etc.).
Available skills:
search, scrape, data-feeds, bright-data-mcp, bright-data-best-practices
brightdata add mcp
Add the Bright Data MCP server to Claude Code, Cursor, or Codex. Uses the API key stored by brightdata login.
Config file locations
The command writes the MCP server entry under
mcpServers["bright-data"]. Existing config is preserved - only the bright-data key is added or replaced.
instagram_profiles<url>instagram_posts<url>instagram_reels<url>instagram_comments<url>facebook_posts<url>facebook_marketplace_listings<url>facebook_company_reviews<url> [num_reviews]facebook_events<url>tiktok_profiles<url>tiktok_posts<url>tiktok_shop<url>tiktok_comments<url>x_posts<url>youtube_profiles<url>youtube_videos<url>youtube_comments<url> [num_comments]reddit_posts<url>