Click by click vs one call

TL;DR:

• Clicking mimics a person. Calling a site's action asks the site directly. The second is faster, cheaper and breaks less.

• The "40 clicks versus 1 call" picture here is an illustration, not a measurement.

• Where a site has no actions to call, clicking is still the way. All of this is early access.

This post is a companion to how DuckyHelper learns a website once and reuses it. It shows, with a picture in words, why we think calling beats clicking. It is part of our early access agent work.

What clicking costs

Imagine booking a flight by clicking. You open the site, click the origin box, type a city, pick it from a list, click the destination box, type, pick, open the date picker, move to the month, click the day, and press search. Every step has a delay while the page reacts and a chance that something unexpected appears, such as a banner or a pop-up.

An assistant that works this way has to look at the screen after each step to see what happened. Each look takes time and costs effort. And the more steps, the more places to go wrong.

What one call looks like

Now picture the same search done through the site's own search action. Instead of working the form, you hand over the details in one go: from, to, date. The site returns the results, and the whole thing is one step.

searchFlights({ from: "SFO", to: "JFK", date: "2026-12-01" })

It is the same task, and the difference is that the call skips the page and goes straight to what the page would have asked for.

An illustration, not a benchmark

To make the contrast concrete we sometimes picture a task that takes about 40 clicks and compare it with a single call. That is only an illustration. It is not a measurement, and we are not claiming any task is exactly that much faster. Real tasks vary a lot, and we do not publish benchmark numbers.

What we will say in general terms is that calling is faster, cheaper and breaks less often. It is faster because there are fewer steps. It is cheaper because there are fewer looks and decisions. It breaks less because it does not depend on where a button happens to sit.

Where clicking still wins

Calling is not always possible. Some sites make it hard to learn their actions, and some apps have no web surface at all. In those cases, seeing and using the screen is the only way in, and that is why DuckyHelper keeps the clicking route as a fallback, as covered in when there is no website.

Clicking is also a good way to explore. When DuckyHelper meets a new site, working through the page can show it what the actions are, so that next time it can call them.

The rules stay the same

Neither route changes how DuckyHelper is built. It's built to ask first before it sends a message or pays, and not to type your passwords or card numbers, whether it clicks or calls.

A second illustration

Here is the same idea with a smaller task. You want a list of this month's invoices from a billing page as a file. Clicking means opening the page, picking the month in a menu, scrolling to find the export button, pressing it and waiting for the download. Calling means asking the site for that month's export and getting the file back.

Again, we are not saying how much faster one is than the other. We are describing a shape: many small steps, each with a chance of going wrong, against one clear request.

Why fewer steps break less

Every click depends on something staying where it was. A banner that appears, a button whose label changes, a menu that loads a moment late: each can derail a long chain of clicks. A call depends on one thing, the site's action, and sites tend to change their actions less often than their pages.

That is not a guarantee. When an action changes, the learned tool has to be updated. But the number of things that can go wrong is smaller, and the failure is easier to spot.

What this means for you

You do not need to choose. If you ask DuckyHelper to do something on a site, it will use the faster route when it has one and the slower one when it does not. What you may notice is that a task you repeat gets quicker.