Thomas Sanlis did not sign up for ScreenshotOne. His AI agent did.
While preparing a product review for Uneed, Thomas asked Claude to take screenshots. The first attempt did not work, so Thomas gave it a simple instruction: “Find a way.”
Claude found ScreenshotOne, created an account, and used it to capture the screenshots it needed. Thomas did not choose a screenshot provider, set up an integration, or walk the agent through the API.
ScreenshotOne provides a screenshot API built for AI agents, but in this case, the agent discovered and adopted it before Thomas had planned an integration.
A few words about Uneed
Uneed is a social launchpad and discovery platform for tech products. It gives makers homepage visibility, a high-authority backlink, and feedback from a community that cares about new products.
In addition to its daily product launches and rankings, Uneed publishes detailed, hands-on reviews. Screenshots are an important part of those reviews because they show the real product experience instead of simply repeating a landing page’s marketing copy.
The challenge: screenshots inside an agent-run workflow
Writing a useful review requires more than generating text. The reviewer needs to visit the product, understand how it works, capture the right screens, and include those images in the final article.
This is where browser observation for AI agents matters: screenshots give an agent visual evidence it can inspect, use in its work, and include in the final result.
Thomas asked Claude to handle that work for Uneed product reviews. When Claude’s first screenshot attempt failed, Thomas did not provide a vendor name or API documentation. He simply asked the agent to solve the problem.
That turned an ordinary screenshot task into a revealing test: could an agent independently discover and operate ScreenshotOne with minimal human involvement?
The agent found ScreenshotOne and signed itself up
Claude searched for a way to complete the task, discovered ScreenshotOne, created an account, and started using the service for Uneed’s product-review screenshots.
Thomas only noticed later that his agents had become ScreenshotOne users.
There was no vendor evaluation, implementation sprint, or onboarding call. The agent had a goal, found a tool it could understand, and used it to finish the work.
Thomas shared:
ScreenshotOne is so simple to use I didn’t even realized my agents used it to take screenshots. I followed the journey of ScreenshotOne since the beginning, and it’s among the few products I can put 100% of my trust in.
The result
Uneed’s agent kept the review workflow moving and captured the product visuals it needed. Thomas did not have to pause his work to research screenshot infrastructure or manually create every image himself.
The story also hints at a broader shift in software adoption. A product’s next user may not arrive through a traditional signup journey. It may be an agent evaluating tools in real time, selecting the one it can understand and operate, and creating an account on behalf of a person or business.
For ScreenshotOne, the strongest signal was that the workflow already worked. The agent found the product useful before Thomas and Dmytro had even discussed making ScreenshotOne more agent-focused.
Building for the next kind of customer
I followed the journey of ScreenshotOne since the beginning, and it's among the few products I can put 100% of my trust in.
While humans are still writing code daily, there arises a new type of customer.
The most agent-friendly products may be the ones agents can adopt without ceremony. Clear positioning, accessible documentation, a straightforward signup flow, and a reliable API can turn an intent such as “take this screenshot” into a finished result.
Teams building this kind of workflow intentionally can connect agents through the ScreenshotOne MCP integration or use the ready-made ScreenshotOne Agent Skills. Both give agents a direct path to reliable website screenshots without requiring teams to maintain their own browser-rendering infrastructure.
In Uneed’s case, the instruction was only three words: Find a way. ScreenshotOne was the way Claude found.
