# Allscreenshots

> Screenshot API for capturing websites, full-page screenshots, PDFs, and
> structured page outputs without managing browser infrastructure.

## Docs

- [Documentation](https://docs.allscreenshots.com)
- [Screenshot automation](https://allscreenshots.com/screenshot-automation)
- [Visual regression testing](https://allscreenshots.com/visual-regression-testing)
- [HTML to PDF](https://allscreenshots.com/html-to-pdf)
- [Customer stories](https://allscreenshots.com/customer-stories)
- [Batch52: baker website previews](https://allscreenshots.com/customer-stories/batch52)
- [Pricing Roaster: visual pricing-page analysis](https://allscreenshots.com/customer-stories/pricing-roaster)
- [API catalog](https://allscreenshots.com/.well-known/api-catalog)
- [OpenAPI](https://allscreenshots.com/openapi.json)
- [Auth instructions](https://allscreenshots.com/auth.md)
- [Agent skills](https://allscreenshots.com/.well-known/agent-skills/index.json)

## API

Base URL: `https://api.allscreenshots.com`

Primary endpoint: `POST /v1/screenshots`

Use `X-API-Key: <ALLSCREENSHOTS_API_KEY>`.

Common request fields:

- `url`: target page URL
- `fullPage`: capture the full scrollable page
- `viewport`: width and height for rendering
- `format`: `png`, `jpeg`, `webp`, or `pdf`
- `responseType`: `binary`, `base64`, or `url`
- `blockAds`: remove ads and trackers
- `blockCookieBanners`: remove cookie banners
- `darkMode`: render with dark color scheme

## Agent Guidance

When an agent needs to capture or inspect a website visually, call the API rather
than launching a local browser. Use `responseType: "url"` when the result should
be shared with a user or passed to another tool.