ScreenshotOne is a screenshot API for developers, enabling the rendering of website screenshots through simple API calls without managing browser clusters.
ScreenshotOne is a screenshot API for developers, enabling the rendering of website screenshots through simple API calls without managing browser clusters. On Nagent, ScreenshotOne is exposed as a fully-configurable developer tools integration that any agent can call — 5 actions, and API key authentication. No code is required to wire ScreenshotOne into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use ScreenshotOne to automate the kinds of tasks developer tools teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire ScreenshotOne into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against ScreenshotOne, with input parameters and output schema. Drop these into any step of an agent built in Helix.
SCREENSHOTONE_GET_USAGETool 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SCREENSHOTONE_LIST_DEVICESTool 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.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SCREENSHOTONE_TAKE_ANIMATED_SCREENSHOTThis 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).
Input parameters
The URL of the website to capture.
Delay before taking the screenshot in milliseconds. Set non-zero to allow heavy or complex pages to fully render before capture begins.
Width of the output animation. If specified, height must also be specified. Defaults to viewport width. Unset or misconfigured viewport_width/viewport_height can cause cropping or distortion when width is not explicitly set.
X-coordinate for clipping the video. Only for GIF format.
Y-coordinate for clipping the video. Only for GIF format.
The format of the animated screenshot.
Height of the output animation. If specified, width must also be specified. Defaults to viewport height.
Duration of the animation in seconds. Minimum 1, maximum 30.
Defines the animation behavior. `default` records the site as it appears after loading. `scroll` simulates scrolling.
Block ads.
Capture the full scrollable page (Note: for animated, this might interact with scenario). Very long pages produce extremely tall output that may cause downstream display or storage issues.
Pixels to scroll per step. Applicable if scenario is 'scroll'.
Width for clipping the video. Only for GIF format.
Height for clipping the video. Only for GIF format.
Scroll back to the top after reaching the bottom. Applicable if scenario is 'scroll'.
Aspect ratio for the animation (e.g., '16:9'). If specified, width and height are ignored.
Delay in milliseconds between scrolls. Applicable if scenario is 'scroll'.
Scrolling easing effect. Applicable if scenario is 'scroll'.
Viewport width.
Omit background (only for MOV format).
Stop recording animation when full scrolling is completed. Applicable if scenario is 'scroll'.
Duration in milliseconds of one scroll. Applicable if scenario is 'scroll'.
Viewport height.
Wait time in milliseconds before starting scrolling. Applicable if scenario is 'scroll'.
Device scale factor.
Scroll to the end after the specified duration in milliseconds with the specified easing in one scroll. Applicable if scenario is 'scroll'.
Navigate while scrolling and record the new opened page. Applicable if scenario is 'scroll'.
Block cookie banners.
Scroll till the CSS selector is visible. Applicable if scenario is 'scroll'.
Algorithm for scrolling back (`once` or `repeat`). Applicable if scenario is 'scroll'.
Navigate after duration in milliseconds (default is half of the duration). Applicable if scenario is 'scroll'.
URL to navigate to. Applicable if scenario is 'scroll'.
Scroll immediately or wait for scroll_delay. Applicable if scenario is 'scroll'.
Scroll back after the specified duration in milliseconds. Applicable if scenario is 'scroll'.
Hints for links to use for navigation if scroll_navigate_to_url is not specified. E.g. \['pricing', 'about'\]. Applicable if scenario is 'scroll'.
Stop scrolling after the specified duration in milliseconds. Use with scroll_complete=false and scroll_back=false. Applicable if scenario is 'scroll'.
Adjust the top position of the selector in the viewport. Applicable if scenario is 'scroll'.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SCREENSHOTONE_TAKE_BULK_SCREENSHOTSTool 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.
Input parameters
Execute all screenshot requests immediately instead of lazy loading. When false (default), screenshots are taken when downloaded. When true, screenshots are taken immediately.
Default options applied to all screenshot requests in the bulk operation.
Optimize bulk screenshots for same URLs with different parameters. Only works when execute=true. Improves performance when taking multiple screenshots of the same site.
Array of individual screenshot requests. Maximum 20 requests per bulk call.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
SCREENSHOTONE_TAKE_SCREENSHOTTool 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.
Input parameters
URL of the website to screenshot. Either url, html, or markdown must be provided.
HTML content to render. Either url, html, or markdown must be provided.
Set to true to get cached screenshot URL when response_type is 'json'. The response will include a cache_url field.
Delay in seconds to wait before rendering the screenshot. Must be between 0 and 30 seconds.
Output format for the screenshot.
Markdown content to render. Either url, html, or markdown must be provided.
Block ads on the page.
Enable dark mode for rendering the page.
Block chat widgets on the page.
Response type for the screenshot.
Viewport width of the browser in pixels.
Viewport height of the browser in pixels.
Device scale factor of the viewport. Must be between 1 and 5.
Block cookie banners on the page.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 46 agents privately built on Nagent that already use ScreenshotOne.
Build on Nagent
Connect ScreenshotOne to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find ScreenshotOne, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, ScreenshotOne is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once ScreenshotOne is connected, you configure its 5 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop ScreenshotOne steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a ScreenshotOne event fires, the agent kicks off automatically.
Every ScreenshotOne action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While ScreenshotOne ships with 5 pre-built developer tools actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching ScreenshotOne together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build ScreenshotOne-based workflows tailored to your business.