|
|
|
|
|
by arjunchint
8 days ago
|
|
Who are your primary customers/usecases? What do you think of just reverse engineering the network requests and writing scripts to hit the underlying APIs that the browser is making instead of tackling at the browser automation layer? |
|
Our Intuned agent and Web Task API always use reverse engineering when possible — the underlying agents have access to the network layer and can reverse engineer APIs when needed. At the end of the day, this comes down to what the user needs. We have seen cases where users need data from the network, and in these cases we skip the browser layer. In some other cases, we saw that users need to authenticate via the browser but then all the automation can be done via the network. We have also seen customers who want to get markdown of the pages in addition to hitting the APIs so a browser layer is a must.