Screenshot API

I redesigned the pricing page for @DmytroKrasun Screenshot One. What do you think? By redesigned, I mean I sent a message to Claude to redo it. Which do you prefer? Link to Claude's version: claude.ai/public/artifac…

Thank you @ScreenshotOneHQ ( and @DmytroKrasun ) for sponsoring @coolifyio. 💜 We now have 3 huge sponsors! 🤯

This doesn't feel real, @ScreenshotOneHQ. #orpc #opensouce #github

Build your product with a public API in mind, so if needed in the future, AI agents can use it. oRPC supports that (with OpenAPI) out of the box. It provides everything that API routes, Server Functions, and tRPC offer, but even more than that and in a coherent way without any additional dependencies. screenshotone.com/blog/migration…

I used ScreenshotOne for LandingMRR. It was probably the only reason I was able to ship in 36 hours instead of multiple days or weeks. Similarly to the app in the video, the quality of my app directly depends on the quality of the screenshots. Next up is separating screenshots by sections by css selectors to the request. Thanks for the great product!

@DmytroKrasun @ScreenshotOneHQ Greaaaatttt idea!

Website screenshots for OpenClaw 👉 screenshotone.com/openclaw/ ✨

Code review matters. People who post the opposite: 1. Are parroting to get attention. 2. Or they don't have experience in engineering or building mostly CRUD. 3. Or they are selling vibe coding platforms. LLMs don't have coherent understanding of your codebase (yet). They generate code that **might** work. It is on you to understand and test their output.

@_lhermann @DmytroKrasun 👋

@DmytroKrasun Now you need a @screenshotone_status account

Currently experiencing a temporary reduction in performance for some ScreenshotOne API requests. The root cause has been identified: our main cluster did not scale due to a shortage of compute resources. Traffic is being rerouted through additional resources and data centers. Performance should already be back to normal.

My thesis always was: If I can get one paying customer, I will be able to find 10 more. If I have 10 more, I will find 100. Soon (hopefully), I will get to 1000 paying customers. But! I will not reach 10,000 paying customers in the same niche with the same product. I have some time to figure out what to do next and how to scale. Adding more services? New products? Agents?

My tiny product (ScreenshotOne.com) is now officially serving 800+ paying customers 🥳 Thanks to everyone who supported me in this journey 🙏

If you need screenshots of web UI I would 100% recommend ScreenshotOne, used it for framekit.ai and it was seamless 😁 Reasons why I didn’t build it myself are in the blog post Great work @DmytroKrasun !

One of my favorite use cases for ScreenshotOne 👉 screenshotone.com/blog/framekit/ A few thoughts on why:

Use ScreenshotOne and viaSocket integration for screenshot automation workflows 👉 screenshotone.com/blog/screensho…

@softranking5 @DmytroKrasun Thank you ❤️🙏

Huge congrats to the @ScreenshotOneHQ & @DmytroKrasun on building a screenshot API that truly simplifies the developer experience! Your Product is live on SoftRankings. Explore the listing → softrankings.com/products/scree…

Last week on Saaspo

Talked with @forgebitz about how they use ScreenshotOne in Promptwatch and why they decided to buy instead of build. I don't know how long that equation will last. Maybe, at some point building with AI will be a no-brainer versus buying, but once again our conversation reminded me that to win you need to focus on your customers and your core competitive advantage; everything else can be bought/outsourced. screenshotone.com/blog/promptwat…