canonical: https://jentic.com/apis/browsersolver.com/browsersolver

# BrowserSolver API Reference

The BrowserSolver API fetches public web pages through a ladder of tiers: a fast Crawler pull for static HTML, a managed browser Rendering session for script-heavy pages, and WebUnlocker for whitelisted retail and marketplace hosts that still block with bot challenges. It also renders any public URL to a PNG, JPEG, WebP, or PDF screenshot, names the bot-protection vendor in front of a URL, and maps the CMS, frameworks, analytics, and CDN a site exposes. Long calls can run as background jobs with is_async=true and be polled on a jobs endpoint, and every call is billed in credits that the usage endpoint reports.

## For AI agents

Fetch HTML from public pages via crawler, headless rendering, or WebUnlocker tiers, take full-page screenshots, detect anti-bot vendors, and identify a site's technology stack.

## Scope

Does not handle proxy pool management, structured product parsing, search engine results, or site hosting. Use for fetching, rendering, screenshotting, and fingerprinting public web pages only.

## Capabilities

- Pull static HTML from a public URL with the Crawler tier, or relay a JSON POST to an upstream endpoint
- Render a JavaScript-heavy page in a managed browser and return the HTML after scripts finish, with wait_for and block_ads controls
- Unlock retail and marketplace hosts on your account whitelist through the WebUnlocker tier when bot challenges persist
- Capture a PNG, JPEG, WebP, or PDF screenshot of a URL with device emulation, full_page capture, and remove_cookie_banners
- Identify the bot-protection vendor in front of a URL before choosing a fetch tier
- Detect the CMS, frameworks, analytics, and CDN a public site uses, in simple or expert mode
- Run any fetch as a background job with is_async and poll its status and result by job id

## Use cases

### AI research agent reading pages it cannot fetch directly

An AI agent asked to summarise a web page often hits client-side rendering or a bot wall that a plain HTTP request cannot get past. Through Jentic the agent searches for 'render a web page', loads the BrowserSolver website-rendering operation, and calls GET `/v1/website/rendering` with the target in the query parameter, with the x-api-key header injected by Jentic. If the page still blocks, the agent can check GET `/v1/website/antibot` and escalate only as far as needed.

Example prompt: Call GET `/v1/website/antibot` for a URL, then fetch it with GET `/v1/website/crawler` if unprotected or GET `/v1/website/rendering` with wait_in_seconds=3 if protected, and summarise the returned HTML

### Visual snapshots for monitoring and reports

Teams tracking landing-page changes or building visual reports need consistent screenshots without running Chromium themselves. BrowserSolver's screenshot operation accepts a url and returns PNG, JPEG, WebP, or PDF output, with device presets such as iphone_14_pro and pixel_7_pro, viewport_width and viewport_height, full_page capture, a CSS selector, and remove_cookie_banners to keep consent dialogs out of the frame.

Example prompt: POST `/v1/website/screenshot` with url, format 'png', device 'iphone_14_pro', full_page true, and remove_cookie_banners true, then store the image

### Technology stack lookup for prospecting

Sales and competitive research often starts with knowing which CMS, analytics, CDN, and security tooling a site runs. GET `/v1/website/technology` maps these from a public URL, returning a simple list or, in expert mode, metadata with confidence scores, at one credit per call according to the spec.

Example prompt: Call GET `/v1/website/technology` for a list of five competitor URLs in expert mode and tabulate the detected CMS and CDN for each

### Batch fetching with background jobs

Large fetch runs are easier to manage asynchronously. Passing is_async=true on any website operation makes BrowserSolver answer with a job_id, and GET `/v1/jobs/{id}` reports progress from 0 to 100 and the result until the status is terminal, such as CompletedJob or Error. Polling is free per the spec, and GET `/v1/usage` shows the credit balance as the batch runs.

Example prompt: Start GET `/v1/website/rendering` with is_async=true for each URL in a list, poll GET `/v1/jobs/{id}` until status is CompletedJob or Error, then check GET `/v1/usage`

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/v1/website/crawler` | Fetch static HTML without a browser |
| GET | `/v1/website/rendering` | Render a page in a managed browser |
| GET | `/v1/website/webunlocker` | Unlock a whitelisted host behind bot challenges |
| POST | `/v1/website/screenshot` | Capture a screenshot or PDF of a URL |
| GET | `/v1/website/antibot` | Identify the bot-protection vendor |
| GET | `/v1/website/technology` | Detect a site's technology stack |
| GET | `/v1/jobs/{id}` | Poll an async job |
| GET | `/v1/usage` | Read usage and credit balance |

## Key resources

- **Website fetch tiers** — Crawler, Rendering, and WebUnlocker operations that return a page's HTML at increasing levels of browser and unlock support
- **Screenshots** — Render a URL to PNG, JPEG, WebP, or PDF with device, viewport, and selector options
- **Site analysis** — Anti-bot vendor detection and technology stack mapping for a public URL
- **Jobs** — Status, progress, and results for requests started with is_async
- **Account** — Usage statistics, credit balance, and infrastructure health stats

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 57 / 100
- **Maturity:** Foundational
- **Dimensions:**
  - Foundational Compliance: 65 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 37 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 77 / 100
- **View full report:** https://jentic.com/apis/browsersolver.com/browsersolver/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring BrowserSolver by hand means attaching the x-api-key header to each call, deciding which fetch tier to escalate to, and building your own polling around is_async jobs. Through Jentic you install once, import BrowserSolver from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** BrowserSolver carries the target URL in a query parameter or the request body, not in the path, so rules bound which operations your agent may call, not which sites it fetches. You choose the operations it may call, so higher-cost ones like the WebUnlocker tier or screenshots are not included unless you add them.
- **Credential handling:** Your BrowserSolver API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'render a web page' or 'detect a website's tech stack', and Jentic returns the matching BrowserSolver operation with its input schema so the agent calls the right tier without reading the docs.

## Related APIs

- **Firecrawl API** — Crawl and scrape sites into LLM-ready markdown rather than raw HTML tiers.
- **ZenRows API** — Scraping proxy with JavaScript rendering and anti-bot bypass.
- **BuiltWith Domain API** — Historical technology profiles for a domain.
- **Browserless REST API** — Hosted headless Chrome with REST endpoints for content, PDF, and screenshots.

## FAQ

### What authentication does the BrowserSolver API use?

Per its OpenAPI spec, the BrowserSolver API authenticates with an API key under the ApiKeyAuth scheme, sent in the x-api-key request header on every request. Through Jentic the key is held by your own instance and attached at call time, so the agent never handles it.

### Which fetch tier should my agent use?

The spec describes a ladder: GET `/v1/website/crawler` is a fast HTTP pull with no browser for pages whose first response already has the content, GET `/v1/website/rendering` runs a managed browser for client-side rendered pages, and GET `/v1/website/webunlocker` handles retail and marketplace hosts on your account whitelist that still block. GET `/v1/website/antibot` names the bot-protection vendor so the agent can pick a tier before spending credits.

### How much does a BrowserSolver call cost?

Calls are billed in credits. The spec lists Crawler, Technology, and Antibot at 1 credit per call, Rendering and Screenshot at 2 credits, and WebUnlocker at 3 credits. Polling GET `/v1/jobs/{id}` is free, and GET `/v1/usage` returns your current usage and credit balance.

### What are the rate limits for the BrowserSolver API?

The OpenAPI spec does not specify request rate limits; it meters usage in credits instead. Check https://browsersolver.com for current plan limits, and use GET `/v1/usage` to read your remaining balance.

### Is there a BrowserSolver MCP server?

You don't need an MCP server to give your agent BrowserSolver. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the crawler, rendering, or screenshot operation it needs, discovered on demand instead of preloaded into its context.

### Can I limit what my agent is allowed to do with BrowserSolver?

Yes. For example, allow only GET `/v1/website/crawler`, GET `/v1/website/antibot`, and GET `/v1/jobs/{id}`, so the agent can do cheap fetches and poll jobs but cannot call the 3-credit WebUnlocker tier or the screenshot operation. Every call it makes is logged.

### How do I take a screenshot through Jentic?

Add BrowserSolver to your Jentic One instance from the directory and store your x-api-key. Your agent searches for 'screenshot a web page', loads the post-website-screenshot operation, and sends POST `/v1/website/screenshot` with a url and a format such as png or pdf. To run it on your own infrastructure, install Jentic One from its GitHub repo.
