Where an API stops

Ordinary jobs that stop because there is nowhere to put a program.

Agents can drive anything with an API. The gap is everything else: a BIOS screen, a GUI installer, a UAC prompt, an appliance with a web UI and no credentials worth scripting, a vendor box that is locked down, a laptop that will not run an agent. So we go in the other way.

In the way a person would go in.

The machine cannot tell it is not a person, so every screen someone can operate becomes operable.
The full range of what a keyboard and mouse can do, not a crude approximation of it.
The equipment stays as its maker shipped it. None of it becomes ours to keep working.
Nothing is installed on the machine being driven, so there is nothing to package, deploy or maintain on the far end.

The loop

Target machine BIOS, installer, appliance, locked box NOTHING INSTALLED the screen what it sees typing, clicking what it does Agent Machine Interface equipment the operator owns frames intent The agent one way in, and it is locked