# ScreenshotOne AI integration on Definable

> ScreenshotOne is a screenshot API for developers, enabling the rendering of website screenshots through simple API calls without managing browser clusters.

## What this connects

ScreenshotOne is a screenshot API for developers, enabling the rendering of website screenshots through simple API calls without managing browser clusters.

Vendor: https://screenshotone.com/

## Tools available

**5** tools available. First 5:

- `SCREENSHOTONE_GET_USAGE` — Get Usage — Tool to retrieve current API plan usage information. Returns total requests allowed, available requests remaining, used requests count, and concurrency limits for the current billing period.
- `SCREENSHOTONE_LIST_DEVICES` — List Devices — Tool to retrieve the list of supported devices for viewport emulation. Use when you need to get available device IDs and their viewport configurations for device emulation in screenshot operations.
- `SCREENSHOTONE_TAKE_ANIMATED_SCREENSHOT` — Take Animated Screenshot — This tool captures an animated screenshot (video or GIF) of a given website URL. It allows customization of the animation format, duration, viewport dimensions, and animation scenario (e.g., scrolling).
- `SCREENSHOTONE_TAKE_BULK_SCREENSHOTS` — Take Bulk Screenshots — Tool to take multiple screenshots in a single request with shared defaults and individual overrides. Use when you need to capture screenshots of multiple URLs or the same URL with different parameters. Supports lazy loading (default) where screenshots are taken on download, or immediate execution with execute=true.
- `SCREENSHOTONE_TAKE_SCREENSHOT` — Take Screenshot — Tool to generate a screenshot or PDF of a website, render HTML, or Markdown using POST request. Use when you need to capture webpage content in various formats (PNG, JPEG, WebP, PDF, HTML). Supports both returning binary content directly or getting a cached URL via JSON response.

## Auth

Auth schemes: `API_KEY`.

## How agents use ScreenshotOne

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

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

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

## Categories

- developer tools — https://definable.ai/apps/category/developer-tools/
- images & design — https://definable.ai/apps/category/images-&-design/

## Related

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