# Hyperbrowser AI integration on Definable

> Hyperbrowser is a next-generation platform empowering AI agents and enabling effortless, scalable browser automation.

## What this connects

Hyperbrowser is a next-generation platform empowering AI agents and enabling effortless, scalable browser automation.

Vendor: https://www.hyperbrowser.ai/

## Tools available

**42** tools available. First 12:

- `HYPERBROWSER_ADD_EXTENSION` — Add Extension — Tool to add a new browser extension to Hyperbrowser for use in sessions. Use when you need to upload a Chrome extension zip file that can be loaded into browser sessions. The extension zip must contain a valid manifest.json file at the root level.
- `HYPERBROWSER_CREATE_PROFILE` — Create Hyperbrowser Profile — Creates a new persistent Hyperbrowser profile for storing browser state (cookies, sessions, etc.). Use this to create a reusable profile that can be attached to browser sessions via the profile ID. Profiles allow you to maintain logged-in states across multiple sessions without re-authenticating.
- `HYPERBROWSER_CREATE_SCRAPE_JOB` — Create Scrape Job — Tool to initiate a new scrape job. Use when you need to extract structured content from a target URL with custom session and scrape settings.
- `HYPERBROWSER_CREATE_SESSION` — Create Session — Tool to create a new browser session with custom stealth, proxy, and privacy settings. Use when initializing an automated browsing session with specific configuration.
- `HYPERBROWSER_DELETE_PROFILE` — Delete Profile — Tool to delete a profile. Use when you need to remove a profile by its unique identifier after confirming its existence.
- `HYPERBROWSER_FETCH_WEB_PAGE` — Fetch Web Page — Tool to fetch a web page and return content in various formats (HTML, Markdown, JSON, screenshot, etc.). Use when you need to retrieve and process web content with customizable browser settings, output formats, and content filtering options.
- `HYPERBROWSER_GET_BROWSER_USE_TASK_RESULT` — Get Browser Use Task Result — DEPRECATED: Use HYPERBROWSER_GET_BROWSER_USE_TASK_STATUS instead. Tool to retrieve the status and results of a browser use task. Use after starting a browser use task to check its progress, retrieve execution steps, and obtain the final result.
- `HYPERBROWSER_GET_BROWSER_USE_TASK_STATUS` — Get browser-use task status — Tool to retrieve the current status of a browser-use task. Use when checking if a browser automation task has completed or is still pending.
- `HYPERBROWSER_GET_CLAUDE_COMPUTER_USE_TASK_RESULT` — Get Claude Computer Use Task Result — Tool to retrieve the complete result and status of a Claude Computer Use task. Use when you need full task details including execution steps, final results, and error information.
- `HYPERBROWSER_GET_CLAUDE_COMPUTER_USE_TASK_STATUS` — Get Claude Computer Use Task Status — Poll the execution status of a Claude Computer Use task. Use after calling HYPERBROWSER_START_CLAUDE_COMPUTER_USE_TASK to check if the task has completed, is still running, or has failed. Pass the jobId returned from the start task action.
- `HYPERBROWSER_GET_CRAWL_JOB_STATUS` — Get Crawl Job Status — Tool to retrieve the status and results of a specific crawl job. Use after submitting a crawl job to check its progress or fetch results.
- `HYPERBROWSER_GET_CRAWL_STATUS` — Get Crawl Status — Tool to retrieve the current status of a specific crawl job. Use after initiating a crawl job to poll its status.

## Auth

Auth schemes: `API_KEY`.

## How agents use Hyperbrowser

Inside a Definable workflow, Hyperbrowser is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Hyperbrowser** — the Researcher (GPT-5.5) pulls context from Hyperbrowser (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Hyperbrowser** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Hyperbrowser (create record, post message, draft email).
- **Designer / Engineer → Distributor → Hyperbrowser** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Hyperbrowser (attach file, open PR comment, post status).

The Verifier checks every Hyperbrowser call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- ai web scraping — https://definable.ai/apps/category/ai-web-scraping/
- ai agents — https://definable.ai/apps/category/ai-agents/

## Related

- HTML page: https://definable.ai/apps/hyperbrowser/
- Same category (ai web scraping): https://definable.ai/apps/category/ai-web-scraping/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt