Back
ScreenshotOne
ScreenshotOne
#screenshotone
Render screenshots in one simple API call, instead of managing browser clusters, and handling all the corner cases.
Load previous page…
Temporarily made the fail_if_content_contains option to match only visible content on the page to help a paying
#screenshotone customer solve their issue. I need to decide if that should be a persistent change, or I should create a new parameter.
Helped a paying
#screenshotone customer to improve rendering of scrolling screenshots by fixing an issue waiting websites to load.
Checked failed requests for a paying
#screenshotone customer—the problem was in the proxies they used, not in the ScreenshotOne API.
Added new option (metadata_icon) to get the icon of any website with
#screenshotone API by a potential paying customer request.
Made metadata options common for most all
#screenshotone rendering requests except metadata image size.
Increased allowed quota for a
#screenshotone user on the free plan with the warning that I won't do it anymore and they will need to pay.
It is costly for me.
Wrote a simple screenshot logs ingestion logic to ClickHouse from MySQL for
#screenshotone. Should I deploy to production? 🤔
Regenerated invoice for the
#screenshotone paying customer—there is a bug of the company not being assigned to the subscription and that lead to the invoice missing it.
Checked affiliates of
#screenshotone and if any of them has earned above the $100 threshold to send money—unfortunately nobody to send to money to, as for now.
Changed the
#screenshotone user email by the support request. Was it probably the second time this month I did it? I need to consider to adding that as a feature.
Published a new blog post about the new
#screenshotone llms.txt feature 👉 screenshotone.com/blog/docs-f….
Made
#screenshotone documentation available for LLMs as screenshotone.com/docs/llms.t… and screenshotone.com/docs/llms-f….