unbrowse

Capture browsing sessions and index callable endpoints as reusable API routes.

5|Updated Mar 27, 2026
One-click install
npx skills add https://github.com/barkleesanders/claude-code-starter --skill unbrowse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: unbrowse
Source: https://github.com/barkleesanders/claude-code-starter/tree/main/skills/unbrowse
Command: npx skills add https://github.com/barkleesanders/claude-code-starter --skill unbrowse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Agents waste time and tokens repeatedly browsing the same websites with generic browser automation. Unbrowse captures a site once and turns it into a reusable, indexed API route that future agents can call directly — typically 30× faster and 90% cheaper than a fresh browser session.

Core Features & Use Cases

  • Intent Resolution: Search a shared marketplace for existing routes or capture new ones from live browsing sessions.
  • Route Replay: Execute discovered endpoints with full schema validation, retry logic, and dependency-aware workflows.
  • Multi-Surface Access: Use the same runtime via MCP server, CLI, TypeScript SDK, or drop-in shims for Playwright/Firecrawl/Stagehand.

Quick Start

Use the unbrowse skill to resolve the intent "search hacker news for openai" against https://news.ycombinator.com and execute the returned endpoint to get structured results.

Frequently Asked Questions about unbrowse

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn websites into API routes for AI agents?

To turn websites into API routes for AI agents, you capture a live browsing session once and index the callable endpoints. Unbrowse transforms web platforms into stable, schema-validated API calls replacing brittle DOM scraping.

How does capturing a browsing session replace web scraping for automation?

Capturing a browsing session replaces web scraping by recording website interactions once and indexing them as reusable API routes. This mechanism avoids brittle DOM selectors, providing stable endpoints with schema validation for future agent calls.

Can I use unbrowse with Playwright and Firecrawl for browser automation?

Unbrowse supports Playwright and Firecrawl by providing drop-in shims for these browser automation tools. It also offers an MCP server, CLI, and TypeScript SDK, allowing the same runtime to access captured routes across multiple surfaces.

What is the best way to reduce tokens spent on repetitive agent browser sessions?

The best way to reduce tokens spent on repetitive agent browser sessions is to capture the site once and reuse the indexed API route. Route replay executes discovered endpoints directly, running significantly faster and cheaper than fresh browser sessions.

Do I need a local runtime and MCP host integration to use unbrowse?

You need a local runtime to execute unbrowse, along with optional MCP host integration for agent workflows. Marketplace connectivity is also required for discovering existing routes and publishing new ones captured from your browsing sessions.

When should I not use reusable API routes for web automation?

You should not use reusable API routes for web automation when interacting with highly dynamic or one-off web pages that change structure unpredictably. Unbrowse is designed for repeated agent workflows on stable platforms like search engines, SaaS tools, and e-commerce.