Use this skill when the user wants to search the web without a full browser session: find URLs, titles, and metadata for a query. Prefer it over a browser when you just need search results, not page content. Returns structured results with titles, URLs, authors, and dates.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Search the web and return structured results — no browser session required.
Get your API key from: https://browserbase.com/settings
export BROWSERBASE_API_KEY="your_api_key"
| Use Case | Search API | Browser Skill |
|---|---|---|
| Find URLs for a topic | Yes | Overkill |
| Get page titles and metadata | Yes | Overkill |
| Read full page content | No | Yes |
| JavaScript-rendered pages | No | Yes |
| Form interactions | No | Yes |
| Speed | Fast | Slower |
Rule of thumb: Use Search to find relevant URLs and metadata. Use the Browser skill when you need to visit and interact with the pages. Use Fetch to retrieve page content without JavaScript rendering.
curl -X POST "https://api.browserbase.com/v1/search" \
-H "Content-Type: application/json" \
-H "X-BB-API-Key: $BROWSERBASE_API_KEY" \
-d '{"query": "browserbase web automation"}'
| Field | Type | Default | Description |
|---|---|---|---|
query | string | required | The search query |
numResults | integer (1-25) | 10 | Number of results to return |
Returns JSON with:
| Field | Type | Description |
|---|---|---|
requestId | string | Unique identifier for the search request |
query | string | The search query that was executed |
results | array | List of search result objects |
Each result object contains:
| Field | Type | Description |
|---|---|---|
id | string | Unique identifier for the result |
url | string | URL of the result |
title | string | Title of the result |
author | string? | Author of the content (if available) |
publishedDate | string? | Publication date (if available) |
image | string? | Image URL (if available) |
favicon | string? | Favicon URL (if available) |
Note: The
@browserbasehq/sdkdoes not have a search method yet. Use cURL or direct HTTP calls.
curl -X POST "https://api.browserbase.com/v1/search" \
-H "Content-Type: application/json" \
-H "X-BB-API-Key: $BROWSERBASE_API_KEY" \
-d '{"query": "web scraping best practices", "numResults": 5}'
| Status | Meaning |
|---|---|
| 400 | Invalid request body (check query and parameters) |
| 403 | Invalid or missing API key |
| 429 | Rate limit exceeded (retry later) |
| 500 | Internal server error (retry later) |
numResults when you only need a few top resultsFor detailed examples, see EXAMPLES.md. For API reference, see REFERENCE.md.
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Analyze an existing web application, identify safe user-visible capabilities across routes, forms, server actions, handlers, and schemas, then implement first-party WebMCP tools and validate discovery and invocation with Stagehand. Use when the user asks to make a codebase agent-ready, expose website features as WebMCP tools, or add WebMCP directly to an app rather than generating a standalone injection script from a URL.
日本語の概要は準備中です。原文の説明を表示しています。
Audit the developer experience of a product, SDK, docs site, or SKILL.md by dropping multiple Claude subagents at it with only a tiny task prompt and real tools (WebFetch, Bash, Write). Agents must discover the docs themselves, install deps, ask for credentials if needed, and attempt real execution. The skill captures each agent's trace — tool calls, retries, wall time, errors — and scores on Setup Friction, Speed, Efficiency, Error Recovery, and Doc Quality, then emits an HTML report with an A–F grade and concrete fixes. Use when the user asks to audit agent experience, test a skill, audit docs for agents, check if a SDK is agent-friendly, validate a SKILL.md, measure agent DX, or benchmark how painful onboarding is for an AI agent. Triggers: 'audit agent experience', 'test this skill', 'audit docs for agents', 'is my SDK agent-friendly', 'run a DX audit', 'agent experience test', 'test my docs', 'how do agents do with my product'.
日本語の概要は準備中です。原文の説明を表示しています。
Self-improving browser automation via the auto-research loop. Iteratively runs a browsing task, reads the trace, and improves the navigation skill (strategy.md) until it reliably passes. Supports parallel runs across multiple tasks using sub-agents. Use when you want to build or improve browser automation skills for specific website tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Automate web browser interactions using natural language via CLI commands. Use when the user asks to browse websites, navigate web pages, extract data from websites, take screenshots, fill forms, click buttons, or interact with web applications. Supports remote Browserbase sessions with Browserbase Identity, Verified browsers, automatic CAPTCHA solving, and residential proxies — ideal for protected websites and JavaScript-heavy pages.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a website's observable HTTP traffic into a best-effort OpenAPI 3.1 spec by analyzing a `browser-trace` capture. Use when the user wants to discover/extract API endpoints from a browser session, build an OpenAPI doc from network traffic, or document a third-party site's XHR/fetch surface for client integration.
日本語の概要は準備中です。原文の説明を表示しています。
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page summaries back into an agent loop so its next iteration learns from the last one.
日本語の概要は準備中です。原文の説明を表示しています。