On Demand Page Rendering

GetScreenshot renders a given URL into an image, which supports checks like confirming a page looks right after a change goes live. A Beam agent reads a request for a specific page, such as one flagged by a deployment record, and calls GetScreenshot to render it within the approved settings, such as viewport size and wait time. The image is added to the relevant record or ticket automatically for reference. Deciding whether a rendered page actually looks correct, versus broken, remains a visual judgment call for a person to make, not something the agent evaluates.

Scheduled Page Archiving

Some pages, such as pricing or terms pages, need a dated image kept on file for compliance reasons. A Beam agent reads a list of approved pages on a schedule, such as daily or weekly, and calls GetScreenshot to render each one, saving the image with a timestamp to the storage location a team has approved. Missing or failed renders get flagged rather than silently skipped. What counts as a meaningful change between two dated images, and whether that needs a closer look, is a decision left to the person checking the archive.

Batch Screenshot Requests

GetScreenshot can render many pages in one pass, which suits a periodic check across a larger site rather than one page at a time. A Beam agent reads an approved list of URLs, such as every page in a sitemap, and submits the batch to GetScreenshot within the volume limits a team has agreed. Completed images get attached to their corresponding record or folder once the batch finishes. Any URL that fails to render after the agreed number of attempts gets added to a list for a person to check manually rather than being retried indefinitely.