Browser Use Skills lets you turn any website into a reusable API, no official API required. 1 prompt or 1 demonstration and we reverse-engineer the HTTP calls into a clean API. Need to download a song? Get 1000 posts in seconds? Generate songs on Suno? Pull videos from social media? Create leads in Salesforce?
We built Browser Use Skills because we kept running into the same problem: the API we needed didn't exist.
Suno AI? No public API. YouTube? Rate-limited and restrictive. Half the tools we wanted to automate had no programmatic access at all.
So we asked: what if you could just show an AI agent how to do something once, and it would reverse-engineer the entire flow into a reusable API?
That's exactly what Browser Use Skills does.
You set a goal, record yourself doing the task (or let our agent figure it out), and we turn that into a hosted endpoint you can call whenever you want.
We've been using this internally for weeks! we've already built 20+ APIs for sites we never thought we'd be able to automate.
Would love your feedback. What's the first API you'd build?
So cool and unlocks a crazy number of use cases. Congrats on the launch guys, can't wait to use this!!
Brilliant, what do I get in the credits in terms of volume of calls?
Impressive launch, Browser Use team. From a clarity & onboarding lens: when a developer opens Browser Use for the first time, what’s the one belief you want them to hold in the first 10-15 seconds? Is it: • “I can turn a website into an API in minutes with no scraping headaches.” Or: • “This tool already understands browser actions and lets me build agents without reinventing automation.” Because in dev/AI tooling the biggest adoption barrier often isn’t features; it’s the user believing this will actually save me time and frustration. Curious how you’re shaping that moment for first-time users.
Thnaks for this launch @saurav_panda3 This is insanely useful — skipping the “wait for an API” era and just building your own. Huge potential for automation workflows, congrats on the launch!
I tried the tool, and it really performed well. Would love to keep using it in the future.
How can i make it work when something is behind a login wall?
I've been following Browser Use for a while now. It's great to see solutions being implemented that don't require expensive AI inference at each workflow API call.
My concerns and feedback 👇
How does Browser Use (especially Skills) handle anti-bot measures that most valuable data access on sites employ? - Browser Use will not work across things like DataDome - Skills platform inherits this issue to a larger extent (No Kasada and others) - Skills platform requires user to fetch cookies each session for antibots, which does not work - This limits use cases to less valuable workflows since valuable web data is guarded behind complex fingerprinting
Look forward to seeing how things develop and what's next!
This is an absolute game-changer for me. I now use skills every day to grab all of the latest news from Hacker News and other news sources deterministically, and all it took was a single prompt.
This is cool. But is the underlying technology using Browser Use? All of the existing Browser Use-based platforms seem to take time to complete a simple task
I wonder how fast the API responds and what’s the rate limit
Hey Product Hunt! 👋
We built Browser Use Skills because we kept running into the same problem: the API we needed didn't exist.
Suno AI? No public API. YouTube? Rate-limited and restrictive. Half the tools we wanted to automate had no programmatic access at all.
So we asked: what if you could just show an AI agent how to do something once, and it would reverse-engineer the entire flow into a reusable API?
That's exactly what Browser Use Skills does.
You set a goal, record yourself doing the task (or let our agent figure it out), and we turn that into a hosted endpoint you can call whenever you want.
We've been using this internally for weeks! we've already built 20+ APIs for sites we never thought we'd be able to automate.
Would love your feedback. What's the first API you'd build?