The monthly forty-click export is a JSON file you POST

A dev team drives a desktop app with input/batch to test it. An agent drives it because the app has no API. You drive it because it's the first of the month and the accounting package wants forty clicks before it hands over a CSV.

The package runs in a container at a display URL. You did the forty clicks once, reading /api/v1/display/mouse/location and the window names as you went, and wrote them down: click-at, type-at, wait, click-at. The whole thing is one POST /api/v1/display/input/batch, up to fifty ordered actions, a per-action result. A hoody-curl schedule fires it at 07:00 on the 1st.

No macro recorder on your laptop. No LLM. No vendor asked for an API.

Test harnesses replay clicks to verify. You replay them to be somewhere else at seven.

Forty clicks became a file, and the file keeps its appointment.