More recently, like many companies, we've been building more automation. And like everyone else, we've seen our automations fail on edge cases—a weirdly formatted invoice our parser can't read, a website layout change that breaks a scraper, etc. Our team would have to manually step in to fix these.
We realized other developers must have this exact same problem, but without a 250-person team on standby. So we connected our old, battle-tested Hub to a new, modern front door: a Human-in-the-Loop (HITL) API. We're calling it browser-work.com.
The idea is simple: when you hit a task that needs a human, you can send it to our team through the API.
Here's how it works:
- You POST a request to our endpoint. The payload contains the context for the task (like a URL) and a set of instructions for the human on what to do.
- The task appears in the Hub, where one of our trained operators can claim it.
- They perform the task exactly as instructed, all within the secure Hub environment.
- When they're done, we send a webhook to your system. The return payload includes the task's output, any notes left by the human, and a detailed log of their actions (e.g., DOM elements they interacted with).
For example, if your automation for paying a utility bill fails, you can pass the task to us. A person will log in, navigate the portal, make the payment, and return a confirmation number.The product is live and we're looking for people with interesting use cases.
I'm Robert, the CIO. If this sounds useful to you, send me a brief email about your use case at robert@apmhelp.com and we can get you started right away.
Happy to answer any questions here.
taylorhou•1d ago