ScreenshotOne for AI agents
Agents read ScreenshotOne at once. Changes and sends are held for a person's approval by default.
About ScreenshotOne
ScreenshotOne is a screenshot API for developers, enabling the rendering of website screenshots through simple API calls without managing browser clusters.
What an agent can do in ScreenshotOne
Every ScreenshotOne action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in ScreenshotOne without asking first. 2 actions.
- 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.
- 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.
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 1 action.
- 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
Changes wait in Needs you
Changes and sends in ScreenshotOne are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
ScreenshotOne questions
Can an agent change data in ScreenshotOne on its own?
Not by default. Changes and sends in ScreenshotOne are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in ScreenshotOne?
This connector lists 2 read actions. Reads run at once, without waiting for approval.
How does ScreenshotOne connect?
It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.