Single-call rendering

screenshot.fyi returns an image of a web page from one API call. A Beam agent fires the call on a trigger, reads back the file, and applies your rule for where it should go. It stores the image against the related record, such as a page being documented or reviewed. When the call fails or the returned image is blank, the agent does not save a broken file; it flags the URL for a person, who checks whether the page was down, slow to load, or now blocks automated capture during the run.

Scheduled page snapshots

screenshot.fyi can capture the same pages on a repeating schedule. A Beam agent triggers each batch, reads every returned image, and files it with a timestamp so a visual history builds over time. Pages that render normally are stored against their record. If an image comes back noticeably different in size or content from the last run, the agent notes the change and notifies a person, who decides whether the page was updated on purpose or something broke, rather than letting the archive quietly record a failed or altered render as normal.

Uniform capture rules

screenshot.fyi accepts settings so captures come out consistent across a set. A Beam agent applies your approved options on every call, reads the result, and stores images that meet the spec against the right record. Consistency lets later comparisons stay fair. When a returned image does not match the requested dimensions or format, the agent holds it and flags a person instead of filing an off-spec file, so a mismatched capture does not slip into a documentation set or a comparison your team treats as reliable and current.