Browshot API

Name: Browshot API API
Brand: Browshot API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsTesting QaapiKey22 EndpointsREST

For Agents

Capture screenshots of any URL across desktop and mobile browsers, run batch and crawl jobs, and host or share the resulting images. Useful for marketing previews, social cards, and SEO reporting agents.

Quickstart

Get started with Browshot API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"capture a website screenshot"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Browshot API API.

Capture a single screenshot of a URL with /api/v1/simple for the fastest path or /api/v1/screenshot/create for full options

Run batch screenshot jobs over many URLs and poll for completion via /api/v1/batch/info

Crawl an entire site and capture every page reached via /api/v1/crawl/create

Host the resulting screenshots on Browshot's CDN or push them to your own bucket via /api/v1/screenshot/host

GET STARTED

Start building with Browshot API API

Explore with Jentic

View OpenAPI Document

Use for: I need to capture a screenshot of a competitor's homepage, Take screenshots of 200 URLs in a single batch operation, Crawl a site and capture every page it reaches, Generate a 600x400 thumbnail of an existing screenshot

Not supported: Does not handle generic browser automation, scraping logic, or PDF rendering — use for screenshot capture, batch and crawl jobs, and screenshot hosting only.

Jentic publishes the only available OpenAPI document for Browshot API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Browshot API, keeping it validated and agent-ready. Browshot is a screenshot-as-a-service platform that captures website screenshots from a fleet of browser instances across desktop and mobile profiles. The API covers single-shot capture via /api/v1/simple and /api/v1/screenshot/create, batch capture for many URLs at once, full-site crawl-and-capture jobs, hosted thumbnails, sharing, and account introspection. It also exposes the underlying instance and browser catalogues so you can choose the right viewport and rendering profile per shot.

Use Cases

Patterns agents use Browshot API API for, with concrete tasks.

★ Social Card and Open Graph Preview Generation

Marketing platforms render dynamic social cards for shared URLs by calling /api/v1/screenshot/create with the target page and a 1200x630 viewport. Browshot returns a hosted image URL that the platform embeds in the Open Graph meta tag. Because Browshot offers many browser instances, the cards render the same way the user's actual viewer will see them — including modern fonts and CSS Grid layouts.

POST /api/v1/screenshot/create with the URL, instance_id for Chrome desktop, and width 1200, height 630, then host the result via /api/v1/screenshot/host

Bulk Site Auditing

SEO and marketing teams audit hundreds of pages by batching screenshots of a list of URLs. The agent calls POST /api/v1/batch/create with the URL list and instance, polls GET /api/v1/batch/info for completion, and pulls thumbnails from /api/v1/screenshot/thumbnail for an at-a-glance review grid. This replaces tab-by-tab manual auditing and gives a documented snapshot for the next quarter's comparison.

POST /api/v1/batch/create with an array of 200 URLs and the desired browser instance, then GET /api/v1/batch/info until status is finished

Cross-Device Visual QA

Front-end teams compare a release candidate against production by capturing the same URL on multiple Browshot instances — desktop Chrome, iPhone Safari, Android Chrome — and diffing the resulting images. The /api/v1/instance/list and /api/v1/browser/list endpoints expose the full catalogue so the agent can pick the right device profiles for the team's target audience.

Loop over three instances (desktop Chrome, iPhone Safari, Android Chrome) calling POST /api/v1/screenshot/create for each, then download the images for visual diffing

AI Marketing Agent Through Jentic

An AI marketing agent uses Jentic to generate preview images for newsletter and social content without holding the Browshot API key. The agent searches for 'capture a website screenshot', loads the schema, and executes the call with the URL it just drafted content about. The hosted image URL goes straight into the email template or Slack post.

Use Jentic to search 'capture a website screenshot', load the browshot.com operation, and execute it for the URL the agent is about to share in a campaign

Key Endpoints

22 endpoints — jentic publishes the only available openapi specification for browshot api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/api/v1/simple

Fast one-shot screenshot capture

POST

/api/v1/screenshot/create

Capture a screenshot with full options

POST

/api/v1/batch/create

Submit a batch of URLs for capture

POST

/api/v1/crawl/create

Start a crawl-and-capture job

GET

/api/v1/screenshot/thumbnail

Generate a thumbnail of an existing screenshot

GET

/api/v1/screenshot/host

Host a screenshot on a CDN

GET

/api/v1/instance/list

List available browser instances

GET

/api/v1/account/info

Get account plan and credit balance

GET

/api/v1/simple

Fast one-shot screenshot capture

POST

/api/v1/screenshot/create

Capture a screenshot with full options

POST

/api/v1/batch/create

Submit a batch of URLs for capture

POST

/api/v1/crawl/create

Start a crawl-and-capture job

GET

/api/v1/screenshot/thumbnail

Generate a thumbnail of an existing screenshot

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Browshot API key is stored encrypted in the Jentic vault. Agents receive scoped execution tokens; the raw key never enters prompts or logs.

Intent-based discovery

Agents search by intent such as 'capture a website screenshot' and Jentic returns the matching Browshot operation with its parameter schema, so the agent can call it without browsing the Browshot docs.

Time to first call

Direct Browshot integration: half a day to a day for auth, instance selection, and async capture handling. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Urlbox

Screenshot-as-a-service API with extensive customisation and full-page rendering

Choose Urlbox when you need very large or full-page captures with fine-grained CSS injection options

Alternative

ApiFlash

Screenshot API with quality, format, and freshness controls

Choose ApiFlash when caching control and predictable quality settings matter more than crawl support

Complementary

Browserless

Headless Chrome with /screenshot, /pdf, and /scrape primitives

Use Browserless when you need to do more than screenshot a URL — render to PDF, scrape, or run a full Playwright script

FAQs

Specific to using Browshot API API through Jentic.

Why is there no official OpenAPI spec for Browshot API?

Browshot does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Browshot API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Browshot API use?

Browshot uses an API key passed as a query parameter (the `apiKey` security scheme in the spec). Through Jentic, the key is stored encrypted in the MAXsystem vault and the agent receives a scoped execution token instead of the raw value.

Can I capture mobile screenshots with Browshot?

Yes. Browshot exposes a catalogue of mobile and desktop instances via GET /api/v1/instance/list. Pick the instance_id matching the device profile you want (for example iPhone Safari) and pass it to /api/v1/screenshot/create.

How do I batch screenshot many URLs through Jentic?

Search Jentic for 'capture screenshots in a batch', load the browshot.com schema, and call POST /api/v1/batch/create with an array of URLs and the desired instance. Poll GET /api/v1/batch/info until the batch finishes, then pull each screenshot.

What are the rate limits for the Browshot API?

The OpenAPI spec does not declare explicit rate limits. Browshot bills per credit; check GET /api/v1/account/info for your plan, remaining credits, and concurrent capture cap before kicking off large batches or crawls.

Does Browshot host the screenshots or do I have to download them?

Both are supported. By default screenshots are stored on Browshot's CDN and accessible via GET /api/v1/screenshot/info; calling /api/v1/screenshot/host returns a hosted URL you can embed directly. You can also pull the binary via /api/v1/screenshot/thumbnail and store it yourself.