GetScreenshot StrawberryGet website screenshot in GetScreenshot, without opening it
One sentence in, and a companion has been through the GetScreenshot account api usages, put them where you can read them, and marked the ones it was not sure about.
Open the account api usage. Check it against something else. Write the change. Move to the next one. That is the GetScreenshot afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing changed until you say so.
What it can do is exactly what GetScreenshot exposes to an account you authorise and nothing beyond it: 2 operations, 2 reads and no writes. In practice that means it can get a website screenshot and get an account API usage, and work across the account api usages and website screenshots.
The GetScreenshot API stops at GetScreenshot. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Can it get website screenshot on its own?
All 2 operations read.
Your account, not a guess at it: a companion can get a website screenshot and get an account API usage, and the full list below is the whole list, with nothing inferred from GetScreenshot's documentation.
The account api usages are what most of this inventory is about, alongside the website screenshots. A companion can hold all 2 of these operations and forty open tabs in the same pass, which is how an afternoon of GetScreenshot admin becomes a queue you review.
- Get Website Screenshot
- Get Account API Usage
Nothing writes back. So what moves the account api usages?
Through the screens you already use.
GetScreenshot exposes no write operation to a connected account, so a companion drives GetScreenshot in the session you are already signed into instead, filling the same forms you would to move a account api usage, and anything consequential stops for an approval card before it happens.
That is the ordinary case rather than the exception. Most of what an account api usage in GetScreenshot touches has no API pointed at it, and a companion is useful precisely because it does not need one.
Can it get website screenshot every morning by itself?
Yes.
Saved as a routine, the GetScreenshot account api usages pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The operations playbook catalogues the other recurring shapes of the planning, the GetScreenshot account api usages sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents